[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated: PDF: no more errors
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated: PDF: no more errors. Added catonano to the copyright authors. |
Date: |
Mon, 29 May 2017 21:57:42 +0200 |
This is an automated email from the git hooks/post-receive script.
ng0 pushed a commit to branch master
in repository gnunet-texinfo.
The following commit(s) were added to refs/heads/master by this push:
new 10e0d09 PDF: no more errors. Added catonano to the copyright authors.
10e0d09 is described below
commit 10e0d0961f159791d695cee06da8a0d032f096df
Author: ng0 <address@hidden>
AuthorDate: Wed May 24 21:49:41 2017 +0000
PDF: no more errors. Added catonano to the copyright authors.
---
developer.texi | 103 +++++++++++++++++++-------------------------------
gnunet.texi | 3 +-
installation.texi | 31 ++++++++-------
user.texi | 111 ++++++++++++++++++++++++++++--------------------------
4 files changed, 115 insertions(+), 133 deletions(-)
diff --git a/developer.texi b/developer.texi
index 07c4234..75ee359 100644
--- a/developer.texi
+++ b/developer.texi
@@ -245,15 +245,14 @@ even those that have literally not a single line of code
in them yet.
GNUnet sub-projects in order of likely relevance are currently:
@table @asis
+
@item svn/gnunet Core of the P2P framework, including file-sharing, VPN and
chat applications; this is what the developer handbook covers mostly
address@hidden
-svn/gnunet-gtk/ Gtk+-based user interfaces, including gnunet-fs-gtk
address@hidden svn/gnunet-gtk/ Gtk+-based user interfaces, including
gnunet-fs-gtk
(file-sharing), gnunet-statistics-gtk (statistics over time),
gnunet-peerinfo-gtk (information about current connections and known peers),
gnunet-chat-gtk (chat GUI) and gnunet-setup (setup tool for "everything")
address@hidden
-svn/gnunet-fuse/ Mounting directories shared via GNUnet's file-sharing on Linux
address@hidden svn/gnunet-fuse/ Mounting directories shared via GNUnet's
file-sharing on Linux
@item svn/gnunet-update/ Installation and update tool
@item svn/gnunet-ext/
Template for starting 'external' GNUnet projects
@@ -266,20 +265,17 @@ GNUnet nodes on testbeds for research, development,
testing and evaluation
@item svn/gnunet-qt/ qt-based GNUnet GUI (dead?)
@item svn/gnunet-cocoa/
cocoa-based GNUnet GUI (dead?)
+
@end table
We are also working on various supporting libraries and tools:
@table @asis
@item svn/Extractor/ GNU libextractor (meta data extraction)
address@hidden
-svn/libmicrohttpd/ GNU libmicrohttpd (embedded HTTP(S) server library)
address@hidden
-svn/gauger/ Tool for performance regression analysis
address@hidden svn/monkey/ Tool for
-automated debugging of distributed systems
address@hidden svn/libmwmodem/ Library for
-accessing satellite connection quality reports
address@hidden svn/libmicrohttpd/ GNU libmicrohttpd (embedded HTTP(S) server
library)
address@hidden svn/gauger/ Tool for performance regression analysis
address@hidden svn/monkey/ Tool for automated debugging of distributed systems
address@hidden svn/libmwmodem/ Library for accessing satellite connection
quality reports
@end table
Finally, there are various external projects (see links for a list of those
@@ -351,8 +347,7 @@ transports (UDP and WLAN, mostly) have restrictions on the
maximum transfer
unit (MTU) for packets. The fragmentation library can be used to break larger
packets into chunks of at most 1k and transmit the resulting fragments
reliabily (with acknowledgement, retransmission, timeouts, etc.).
address@hidden
-transport/ The transport service is responsible for managing the basic P2P
address@hidden transport/ The transport service is responsible for managing the
basic P2P
communication. It uses plugins to support P2P communication over TCP, UDP,
HTTP, HTTPS and other protocols.The transport service validates peer addresses,
enforces bandwidth restrictions, limits the total number of connections and
@@ -1945,27 +1940,22 @@ will not report the failure in any way.
@item @code{GNUNET_FORCE_LOG=";;;;DEBUG" gnunet-arm -s} Start GNUnet process
tree, running all processes with DEBUG level (one should be careful with it, as
log files will grow at alarming rate!)
address@hidden
address@hidden"core;;;;DEBUG" gnunet-arm -s} Start GNUnet process
address@hidden @code{GNUNET_FORCE_LOG="core;;;;DEBUG" gnunet-arm -s} Start
GNUnet process
tree, running the core service under DEBUG level (everything else will use
configured or default level).
address@hidden
address@hidden";gnunet-service-transport_validation.c;;;DEBUG"
-gnunet-arm -s} Start GNUnet process tree, allowing any logging calls from
address@hidden
@code{GNUNET_FORCE_LOG=";gnunet-service-transport_validation.c;;;DEBUG"
gnunet-arm -s}
+Start GNUnet process tree, allowing any logging calls from
gnunet-service-transport_validation.c (everything else will use configured or
default level).
address@hidden
address@hidden"fs;gnunet-service-fs_push.c;;;DEBUG" gnunet-arm -s}
address@hidden @code{GNUNET_FORCE_LOG="fs;gnunet-service-fs_push.c;;;DEBUG"
gnunet-arm -s}
Start GNUnet process tree, allowing any logging calls from
gnunet-gnunet-service-fs_push.c (everything else will use configured or default
level).
address@hidden
address@hidden";;GNUNET_NETWORK_socket_select;;DEBUG" gnunet-arm -s}
address@hidden @code{GNUNET_FORCE_LOG=";;GNUNET_NETWORK_socket_select;;DEBUG"
gnunet-arm -s}
Start GNUnet process tree, allowing any logging calls from the
GNUNET_NETWORK_socket_select function (everything else will use configured or
default level).
address@hidden
address@hidden"transport.*;;.*send.*;;DEBUG/;;;;WARNING" gnunet-arm -s}
address@hidden
@code{GNUNET_FORCE_LOG="transport.*;;.*send.*;;DEBUG/;;;;WARNING" gnunet-arm -s}
Start GNUnet process tree, allowing any logging calls from the components
that have "transport" in their names, and are made from function that have
"send" in their names. Everything else will be allowed to be logged only if it
@@ -2299,9 +2289,11 @@ can be set. In addition, the terminator sign depicted as
@address@hidden, NULL, 0,
After the initialization of transport service, the request message would be
processed. Before handling the main message data, the validity of this message
should be checked out, e.g., to check whether the size of message is correct.
address@hidden size = ntohs (message->size); if (size < sizeof (struct
address@hidden
+size = ntohs (message->size); if (size < sizeof (struct
AddressLookupMessage)) @{ GNUNET_break_op (0); GNUNET_SERVER_receive_done
-(client, GNUNET_SYSERR); return; @} @end example
+(client, GNUNET_SYSERR); return; @}
address@hidden example
Note that, opposite to the construction method of the request message in the
@@ -2924,44 +2916,34 @@ the various services:
@table @asis
address@hidden
-PORT Port number on which the service is listening for incoming TCP
address@hidden PORT Port number on which the service is listening for incoming
TCP
connections. ARM will start the services should it notice a request at this
port.
address@hidden
-HOSTNAME Specifies on which host the service is deployed. Note
address@hidden HOSTNAME Specifies on which host the service is deployed. Note
that ARM can only start services that are running on the local system (but will
not check that the hostname matches the local machine name). This option is
used by the @code{gnunet_client_lib.h} implementation to determine which system
to connect to. The default is "localhost".
address@hidden
-BINARY The name of the service binary file.
address@hidden BINARY The name of the service binary file.
address@hidden
-OPTIONS To be passed to the service.
address@hidden OPTIONS To be passed to the service.
address@hidden
-PREFIX A command to pre-pend to the actual command, for example, running
address@hidden PREFIX A command to pre-pend to the actual command, for example,
running
a service with "valgrind" or "gdb"
address@hidden
-DEBUG Run in debug mode (much verbosity).
address@hidden DEBUG Run in debug mode (much verbosity).
address@hidden
-AUTOSTART ARM will listen to UNIX domain socket and/or TCP port of the
address@hidden AUTOSTART ARM will listen to UNIX domain socket and/or TCP port
of the
service and start the service on-demand.
address@hidden
-FORCESTART ARM will always
address@hidden FORCESTART ARM will always
start this service when the peer is started.
address@hidden
-ACCEPT_FROM IPv4 addresses the service accepts connections from.
address@hidden ACCEPT_FROM IPv4 addresses the service accepts connections from.
address@hidden
-ACCEPT_FROM6 IPv6 addresses the service accepts connections from.
address@hidden ACCEPT_FROM6 IPv6 addresses the service accepts connections from.
@end table
@@ -4094,17 +4076,14 @@ options include:
@table @asis
@item GNUNET_CORE_OPTION_NOTHING No notifications
address@hidden
-GNUNET_CORE_OPTION_STATUS_CHANGE Peers connecting and disconnecting
address@hidden
-GNUNET_CORE_OPTION_FULL_INBOUND All inbound messages (after decryption) with
address@hidden GNUNET_CORE_OPTION_STATUS_CHANGE Peers connecting and
disconnecting
address@hidden GNUNET_CORE_OPTION_FULL_INBOUND All inbound messages (after
decryption) with
full payload
@item GNUNET_CORE_OPTION_HDR_INBOUND Just the @code{MessageHeader}
of all inbound messages
@item GNUNET_CORE_OPTION_FULL_OUTBOUND All outbound
messages (prior to encryption) with full payload
address@hidden
-GNUNET_CORE_OPTION_HDR_OUTBOUND Just the @code{MessageHeader} of all outbound
address@hidden GNUNET_CORE_OPTION_HDR_OUTBOUND Just the @code{MessageHeader} of
all outbound
messages
@end table
@@ -4186,8 +4165,7 @@ from the point of view of the sender. The possible values
are:
@table @asis
@item KX_STATE_DOWN Initial value, never used on the network
address@hidden
-KX_STATE_KEY_SENT We sent our ephemeral key, do not know the key of the other
address@hidden KX_STATE_KEY_SENT We sent our ephemeral key, do not know the key
of the other
peer
@item KX_STATE_KEY_RECEIVED This peer has received a valid ephemeral key
of the other peer, but we are waiting for the other peer to confirm it's
@@ -4618,14 +4596,12 @@ Let's close with a couple examples.
@table @asis
address@hidden
-Average: 10, std dev: 1 Here the estimate would be 2^10 = 1024 peers.@
address@hidden Average: 10, std dev: 1 Here the estimate would be 2^10 = 1024
peers.@
The range in which we can be 95% sure is: [2^8, 2^12] = [256, 4096]. We can be
very (>99.7%) sure that the network is not a hundred peers and absolutely sure
that it is not a million peers, but somewhere around a thousand.
address@hidden
-Average 22, std dev: 0.2 Here the estimate would be 2^22 = 4 Million peers.@
address@hidden Average 22, std dev: 0.2 Here the estimate would be 2^22 = 4
Million peers.@
The range in which we can be 99.7% sure is: [2^21.4, 2^22.6] = [2.8M, 6.3M].
We can be sure that the network size is around four million, with absolutely
way of it being 1 million.
@@ -6378,8 +6354,7 @@ a copy of the data. Similarly for a GET request, all
peers will check their
local database for a result. Setting this option can thus significantly improve
caching and reduce bandwidth consumption --- at the expense of a larger DHT
database. If in doubt, we recommend that this option should be used.
address@hidden
-GNUNET_DHT_RO_RECORD_ROUTE This option instructs the DHT to record the path
address@hidden GNUNET_DHT_RO_RECORD_ROUTE This option instructs the DHT to
record the path
that a GET or a PUT request is taking through the overlay network. The
resulting paths are then returned to the application with the respective
result. This allows the receiver of a result to construct a path to the
@@ -6634,11 +6609,9 @@ resolution, such as CNAME, PKEY or GNS2DNS. Resolving a
record of any of these
types will only work if the respective record type is specified in the request,
as the GNS resolver will otherwise follow the delegation and return the records
from the respective destination, instead of the delegating record.
address@hidden
-only_cached This argument should typically be set to @code{GNUNET_NO}. Setting
address@hidden only_cached This argument should typically be set to
@code{GNUNET_NO}. Setting
it to @code{GNUNET_YES} disables resolution via the overlay network.
address@hidden
-shorten_zone_key If GNS encounters new names during resolution, their
address@hidden shorten_zone_key If GNS encounters new names during resolution,
their
respective zones can automatically be learned and added to the "shorten zone".
If this is desired, clients must pass the private key of the shorten zone. If
NULL is passed, shortening is disabled.
diff --git a/gnunet.texi b/gnunet.texi
index a77d57d..afc7b2d 100644
--- a/gnunet.texi
+++ b/gnunet.texi
@@ -8,7 +8,8 @@
@include version.texi
@copying
-Copyright @copyright{} 2017 ng0
+Copyright @copyright{} 2017 address@hidden
+Copyright @copyright{} 2017 Adriano Peluso
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3 or
diff --git a/installation.texi b/installation.texi
index d15e78e..64368c4 100644
--- a/installation.texi
+++ b/installation.texi
@@ -2713,12 +2713,15 @@ This section describes how to setup the MySQL database
for GNUnet.
Note that the mysql plugin does NOT work with mysql before 4.1 since we need
prepared statements. We are generally testing the code against MySQL 5.1 at
-this address@hidden Reasons for using MySQL
+this point.
+
address@hidden Reasons for using MySQL
address@hidden Reasons for using MySQL
@itemize @bullet
@item
-On up-to-date hardware where mysql can be used comfortably, this@ module will
+On up-to-date hardware where mysql can be used comfortably, this module will
have better performance than the other database choices (according to our
tests).
@@ -2750,13 +2753,15 @@ In @code{gnunet.conf} set in section "DATASTORE" the
value for "DATABASE" to
@item
Access mysql as root:@
address@hidden mysql -u root -p
address@hidden
+$ mysql -u root -p
@end example
and issue the following commands, replacing $USER with the username@
that will be running gnunet-arm (so typically "gnunet"):
address@hidden CREATE DATABASE gnunet;
address@hidden
+CREATE DATABASE gnunet;
GRANT select,insert,update,delete,create,alter,drop,create temporary tables
ON gnunet.* TO $USER@@localhost;
SET PASSWORD FOR $USER@@localhost=PASSWORD('$the_password_you_like');
@@ -2809,8 +2814,10 @@ for a rather dramatic boost in MySQL performance.
However, this reduces the
"safety" of your database as with this options you may loose transactions
during a power outage. While this is totally harmless for GNUnet, the option
applies to all applications using MySQL. So you should set it if (and only if)
-GNUnet is the only application on your system using address@hidden Setup for
-running Testcases
+GNUnet is the only application on your system using MySQL.
+
address@hidden Setup for running Testcases
address@hidden Setup for running Testcases
If you want to run the testcases, you must create a second database
"gnunetcheck" with the same username and password. This database will then be
@@ -3524,8 +3531,7 @@ the use of GNS with your operating system.
At this point in time you have different options depending on your OS:
@table @asis
address@hidden
-Use the gnunet-gns-proxy This approach works for all operating systems
address@hidden Use the gnunet-gns-proxy This approach works for all operating
systems
and is likely the easiest. However, it enables GNS only for browsers, not for
other applications that might be using DNS, such as SSH. Still, using the proxy
is required for using HTTP with GNS and is thus recommended for all users. To
@@ -3534,17 +3540,14 @@ the user who will run the browser (this will create a
GNS certificate authority
(CA) on your system and import its key into your browser), then start
@code{gnunet-gns-proxy} and inform your browser to use the Socks5 proxy which
@code{gnunet-gns-proxy} makes available by default on port 7777.
address@hidden
-Use a
address@hidden Use a
nsswitch plugin (recommended on GNU systems) This approach has the advantage of
offering fully personalized resolution even on multi-user systems. A potential
disadvantage is that some applications might be able to bypass GNS.
address@hidden
-Use
address@hidden Use
a W32 resolver plugin (recommended on W32) This is currently the only option on
W32 systems.
address@hidden
-Use system-wide DNS packet interception This approach is
address@hidden Use system-wide DNS packet interception This approach is
recommended for the GNUnet VPN. It can be used to handle GNS at the same time;
however, if you only use this method, you will only get one root zone per
machine (not so great for multi-user systems).
diff --git a/user.texi b/user.texi
index 181fb9e..287ebdb 100644
--- a/user.texi
+++ b/user.texi
@@ -1209,8 +1209,8 @@ freely chosen by the user. This results in non-unique
name-value mappings as
@address@hidden://www.bob.gnu/, www.bob.gnu}} to one user might be
@address@hidden://www.friend.gnu/, www.friend.gnu}} for someone else.
address@hidden Maintaining your own Zones
address@hidden %**end of header
address@hidden Maintaining your own Zones
address@hidden Maintaining your own Zones
To setup you GNS system you must execute:@
@code{$ gnunet-gns-import.sh}
@@ -1241,8 +1241,8 @@ Similar commands will work for other types of DNS and GNS
records, the syntax
largely depending on the type of the record. Naturally, most users may find
editing the zones using the gnunet-setup GUI to be easier.
address@hidden Obtaining your Zone Key
address@hidden %**end of header
address@hidden Obtaining your Zone Key
address@hidden Obtaining your Zone Key
Each zone in GNS has a public-private key. Usually, gnunet-namestore and
gnunet-setup will access your private key as necessary, so you do not have to
@@ -1259,8 +1259,8 @@ Alternatively, you can obtain a QR code with your zone
key AND your pseudonym
from gnunet-gtk. The QR code is displayed in the GNS tab and can be stored to
disk using the Save as button next to the image.
address@hidden Adding Links to Other Zones
address@hidden %**end of header
address@hidden Adding Links to Other Zones
address@hidden Adding Links to Other Zones
A central operation in GNS is the ability to securely delegate to other zones.
Basically, by adding a delegation you make all of the names from the other zone
@@ -1284,8 +1284,8 @@ Furthermore, if Bob has himself a (public) delegation to
Carol's zone under
"carol", you can access Carol's records under NAME.carol.bob.gnu (where NAME is
the name of Carol's record you want to access).
address@hidden The Three Local Zones of GNS
address@hidden %**end of header
address@hidden The Three Local Zones of GNS
address@hidden The Three Local Zones of GNS
Each user GNS has control over three zones. Each of the zones has a different
purpose. These zones are the
@@ -1299,15 +1299,15 @@ private zone, and the
shorten zone.
@end itemize
address@hidden The Master Zone
address@hidden %**end of header
address@hidden The Master Zone
address@hidden The Master Zone
The master zone is your personal TLD. Names within the @code{.gnu} namespace
are
resolved relative to this zone. You can arbitrarily add records to this zone
and
selectively publish those records.
address@hidden The Private Zone
address@hidden %**end of header
address@hidden The Private Zone
address@hidden The Private Zone
The private zone is a subzone (or subdomain in DNS terms) of your master zone.
It should be used for records that you want to keep private. For example
@@ -1315,8 +1315,8 @@ It should be used for records that you want to keep
private. For example
records separate, if just to know that those names are not available to other
users.
address@hidden The Shorten Zone
address@hidden %**end of header
address@hidden The Shorten Zone
address@hidden The Shorten Zone
The shorten zone can either be a subzone of the master zone or the private
zone.
It is different from the other zones in that GNS will automatically populate
@@ -1334,8 +1334,8 @@ From then on, Bob's webpage will also be available for
you as
called automatic name shortening and is supposed to keep GNS names as short and
memorable as possible.
address@hidden The ZKEY Top Level Domain in GNS
address@hidden %**end of header
address@hidden The ZKEY Top Level Domain in GNS
address@hidden The ZKEY Top Level Domain in GNS
GNS also provides a secure and globally unique namespace under the .zkey
top-level domain. A name in the .zkey TLD corresponds to the (printable) public
@@ -1344,8 +1344,8 @@ respective zone. The .zkey TLD is expected to be used
under rare circumstances
where globally unique names are required and for integration with legacy
systems.
address@hidden Resource Records in GNS
address@hidden %**end of header
address@hidden Resource Records in GNS
address@hidden Resource Records in GNS
GNS supports the majority of the DNS records as defined in
@uref{http://www.ietf.org/rfc/rfc1035.txt, RFC 1035}. Additionally, GNS defines
@@ -1365,8 +1365,8 @@ was encountered) and hence generate a valid @code{.gnu}
name.
GNS currently supports the following record types:
address@hidden NICK
address@hidden %**end of header
address@hidden NICK
address@hidden NICK
A NICK record is used to give a zone a name. With a NICK record, you can
essentially specify how you would like to be called. GNS expects this record
@@ -1374,34 +1374,36 @@ under the name "+" in the zone's database (NAMESTORE);
however, it will then
automatically be copied into each record set, so that clients never need to do
a
separate lookup to discover the NICK record.
address@hidden Example
address@hidden %**end of header
address@hidden@
address@hidden
Name: +; RRType: NICK; Value: bob
address@hidden example
This record in Bob's zone will tell other users that this zone wants to be
referred to as 'bob'. Note that nobody is obliged to call Bob's zone 'bob' in
their own zones. It can be seen as a recommendation ("Please call me 'bob'").
address@hidden PKEY
address@hidden %**end of header
address@hidden PKEY
address@hidden PKEY
PKEY records are used to add delegation to other users' zones and give those
zones a petname.
address@hidden Example
address@hidden %**end of header
address@hidden@
Let Bob's zone be identified by the hash "ABC012". Bob is your friend so you
want to give him the petname "friend". Then you add the following record to
your
zone:
address@hidden
Name: friend; RRType: PKEY; Value: ABC012;
address@hidden example
This will allow you to resolve records in bob's zone under "*.friend.gnu".
address@hidden BOX
address@hidden %**end of header
address@hidden BOX
address@hidden BOX
BOX records are there to integrate information from TLSA or SRV records under
the main label. In DNS, TLSA and SRV records use special names of the form
@@ -1413,8 +1415,8 @@ GUI, you do not get to edit BOX records directly right
now --- the GUI will
provide the illusion of directly editing the TLSA and SRV records, even though
they internally are BOXed up.
address@hidden LEHO
address@hidden %**end of header
address@hidden LEHO
address@hidden LEHO
The LEgacy HOstname of a server. Some webservers expect a specific hostname to
provide a service (virtiual hosting). Also SSL certificates usually contain DNS
@@ -1422,16 +1424,15 @@ names. To provide the expected legacy DNS name for a
server, the LEHO record can
be used. To mitigate the just mentioned issues the GNS proxy has to be used.
The
GNS proxy will use the LEHO information to apply the necessary transformations.
address@hidden VPN
address@hidden %**end of header
address@hidden VPN
address@hidden VPN
GNS allows easy access to services provided by the GNUnet Virtual Public
Network. When the GNS resolver encounters a VPN record it will contact the VPN
service to try and allocate an IPv4/v6 address (if the queries record type is
an
IP address) that can be used to contact the service.
address@hidden Example
address@hidden %**end of header
address@hidden@
I want to provide access to the VPN service "web.gnu." on port 80 on peer
ABC012:@
@@ -1445,16 +1446,17 @@ following lines in the @code{gnunet.conf} configuration
file:@
TCP_REDIRECTS = 80:localhost4:8080@
}
address@hidden A, AAAA and TXT
address@hidden %**end of header
address@hidden A, AAAA and TXT
address@hidden A, AAAA and TXT
Those records work in exactly the same fashion as in traditional DNS.
address@hidden CNAME
address@hidden %**end of header
address@hidden CNAME
address@hidden CNAME
As specified in RFC 1035 whenever a CNAME is encountered the query needs to be
restarted with the specified name. In GNS a CNAME can either be:
+
@itemize @bullet
@item
A zone relative name,
@@ -1464,16 +1466,17 @@ A zkey name or
A DNS name (in which case resolution will continue outside of GNS with the
systems DNS resolver)
@end itemize
address@hidden GNS2DNS
address@hidden %**end of header
address@hidden GNS2DNS
address@hidden GNS2DNS
GNS can delegate authority to a legacy DNS zone. For this, the name of the DNS
nameserver and the name of the DNS zone are specified in a GNS2DNS record.
address@hidden Example
address@hidden %**end of header
address@hidden
address@hidden
Name: pet; RRType: GNS2DNS; Value: gnunet.org@@a.ns.joker.com
address@hidden example
Any query to @code{pet.gnu} will then be delegated to the DNS server at
@code{a.ns.joker.com}.@
@@ -1484,9 +1487,11 @@ if you do not want to start resolution in the DNS root
zone (due to issues such
as censorship or availability).
Note that you would typically want to use a relative name for the nameserver,
-i.e.@
+i.e.
address@hidden
Name: pet; RRType: GNS2DNS; Value: gnunet.org@@ns-joker.+@
Name: ns-joker; RRType: A; Value: 184.172.157.218
address@hidden example
This way, you can avoid involving the DNS hierarchy in the resolution of
@code{a.ns.joker.com}. In the example above, the problem may not be obvious as
@@ -1495,8 +1500,8 @@ nameserver was "ns.gnunet.org". In this case, delegating
to "ns.gnunet.org"
would mean that despite using GNS, censorship in the DNS ".org" zone would
still
be effective.
address@hidden SOA, SRV, PTR and MX
address@hidden %**end of header
address@hidden SOA, SRV, PTR and MX
address@hidden SOA, SRV, PTR and MX
The domain names in those records can, again, be either
@itemize @bullet
@@ -1515,8 +1520,8 @@ clients should use the ZKEY zone as the destination
hostname and GNS-enabled
mail servers should be configured to accept e-mails to the ZKEY-zones of all
local users.
address@hidden The Virtual Public Network
address@hidden %**end of header
address@hidden The Virtual Public Network
address@hidden The Virtual Public Network
Using the GNUnet Virtual Public Network (VPN) application you can tunnel IP
traffic over GNUnet. Moreover, the VPN comes with built-in protocol translation
@@ -1545,8 +1550,8 @@ services, the peer sending the request to the Internet
will be able to observe
and even alter the IP traffic. We will discuss additional security implications
of using the VPN later in this chapter.
address@hidden Setting up an Exit node
address@hidden %**end of header
address@hidden Setting up an Exit node
address@hidden Setting up an Exit node
Any useful operation with the VPN requires the existence of an exit node in the
GNUnet Peer-to-Peer network. Exit functionality can only be enabled on peers
@@ -1602,8 +1607,8 @@ passphrase or shared secret, clients connecting to the
service must somehow
learn the service's name. VPN records in the GNU Name System can make this
easier.
address@hidden Fedora and the Firewall
address@hidden %**end of header
address@hidden Fedora and the Firewall
address@hidden Fedora and the Firewall
When using an exit node on Fedora 15, the standard firewall can create trouble
even when not really exiting the local system! For IPv4, the standard rules
seem
@@ -1623,8 +1628,8 @@ these kinds of problems in general involves setting the
firewall to REJECT
instead of DROP and to watch the traffic using wireshark (or tcpdump) to see if
ICMP messages are generated when running some tests that should work.
address@hidden Setting up VPN node for protocol translation and tunneling
address@hidden %**end of header
address@hidden Setting up VPN node for protocol translation and tunneling
address@hidden Setting up VPN node for protocol translation and tunneling
The GNUnet VPN/PT subsystem enables you to tunnel IP traffic over the VPN to an
exit node, from where it can then be forwarded to the Internet. This section
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [gnunet-texinfo] branch master updated: PDF: no more errors. Added catonano to the copyright authors.,
gnunet <=