[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated: HTML: No more error
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated: HTML: No more errors, apparently, on the surface. |
Date: |
Wed, 31 May 2017 19:47:05 +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 79c1312 HTML: No more errors, apparently, on the surface.
79c1312 is described below
commit 79c1312c4ad0239dcc33eacd38bf25372aa63196
Author: ng0 <address@hidden>
AuthorDate: Wed May 24 21:49:44 2017 +0000
HTML: No more errors, apparently, on the surface.
---
user.texi | 73 ++++++++++++++++++++++++++++++++++++++++++++++-----------------
1 file changed, 53 insertions(+), 20 deletions(-)
diff --git a/user.texi b/user.texi
index 287ebdb..425d255 100644
--- a/user.texi
+++ b/user.texi
@@ -696,6 +696,7 @@ impact users that publish, search or download files.
* File-sharing Namespace Management::
* File-Sharing URIs::
* GNS Configuration::
+* Using the Virtual Public Network::
@end menu
@node File-sharing Concepts
@@ -1167,6 +1168,24 @@ to some kind of index or other entry point into the
namespace.
@menu
* DNS Services Configuration::
* The GNU Name System::
+* Maintaining your own Zones::
+* Obtaining your Zone Key::
+* Adding Links to Other Zones::
+* The Three Local Zones of GNS::
+* The Master Zone::
+* The Private Zone::
+* The Shorten Zone::
+* The ZKEY Top Level Domain in GNS::
+* Resource Records in GNS::
+* NICK::
+* PKEY::
+* BOX::
+* LEHO::
+* VPN::
+* A AAAA and TXT::
+* CNAME::
+* GNS2DNS::
+* SOA SRV PTR and MX::
@end menu
@node DNS Services Configuration
@@ -1259,8 +1278,9 @@ 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
@node 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
@@ -1299,15 +1319,17 @@ private zone, and the
shorten zone.
@end itemize
address@hidden The Master Zone
@node 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
@node 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 +1337,9 @@ 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
@node 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 +1357,9 @@ 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
@node 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 +1368,9 @@ 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
@node 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 +1390,8 @@ was encountered) and hence generate a valid @code{.gnu}
name.
GNS currently supports the following record types:
address@hidden NICK
@node 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
@@ -1384,8 +1409,8 @@ 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
@node PKEY
address@hidden PKEY
PKEY records are used to add delegation to other users' zones and give those
zones a petname.
@@ -1402,8 +1427,8 @@ Name: friend; RRType: PKEY; Value: ABC012;
This will allow you to resolve records in bob's zone under "*.friend.gnu".
address@hidden BOX
@node 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
@@ -1415,8 +1440,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
@node 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
@@ -1424,8 +1449,8 @@ 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
@node 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
@@ -1446,8 +1471,8 @@ following lines in the @code{gnunet.conf} configuration
file:@
TCP_REDIRECTS = 80:localhost4:8080@
}
address@hidden A, AAAA and TXT
address@hidden A, AAAA and TXT
address@hidden A AAAA and TXT
address@hidden A AAAA and TXT
Those records work in exactly the same fashion as in traditional DNS.
@@ -1466,8 +1491,8 @@ 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
@node 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.
@@ -1500,8 +1525,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 SOA, SRV, PTR and MX
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
@@ -1520,8 +1545,14 @@ 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 The Virtual Public Network
address@hidden Using the Virtual Public Network
address@hidden Using the Virtual Public Network
+
address@hidden
+* Setting up an Exit node::
+* Fedora and the Firewall::
+* Setting up VPN node for protocol translation and tunneling::
address@hidden menu
Using the GNUnet Virtual Public Network (VPN) application you can tunnel IP
traffic over GNUnet. Moreover, the VPN comes with built-in protocol translation
@@ -1607,8 +1638,9 @@ 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
@node 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
@@ -1628,8 +1660,9 @@ 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
@node 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: HTML: No more errors, apparently, on the surface.,
gnunet <=