[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated: user.texi: first fi
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated: user.texi: first fixes, copyrights. |
Date: |
Fri, 10 Mar 2017 14:20:10 +0100 |
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 f341dc0 user.texi: first fixes, copyrights.
f341dc0 is described below
commit f341dc073f8389910a10c2f0be362e7c59830054
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:57:54 2017 +0000
user.texi: first fixes, copyrights.
---
user.texi | 236 ++++++++++++++------------------------------------------------
1 file changed, 53 insertions(+), 183 deletions(-)
diff --git a/user.texi b/user.texi
index 67db876..998f111 100644
--- a/user.texi
+++ b/user.texi
@@ -1,30 +1,71 @@
\input texinfo @c -*-texinfo-*-
@c %**start of header
@setfilename user
address@hidden User Handbook
address@hidden User Handbook of GNUnet
@c %**end of header
address@hidden Top
address@hidden
+Copyright @copyright{} 2017 ng0
+Permission is granted to copy, distribute and/or modify this document
+under the terms of the GNU Free Documentation License, Version 1.3 or
+any later version published by the Free Software Foundation; with no
+Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
+copy of the license is included in the section entitled ``GNU Free
+Documentation License''.
+A copy of the license is also available from the Free Software
+Foundation Web site at @url{http://www.gnu.org/licenses/fdl.html}.
-This book documents how to use the various Peer-to-Peer applications of the
GNUnet system. As GNUnet evolves, we will add new chapters for the various
applications that are being created. Comments and extensions are always
welcome. As with all documentation on this page, this is free documentation
available under both the GPLv3+ or the GFDL at your choice (see copyright).
+Alternately, this document is also available under the General
+Public License, version 3 or later, as published by the Free Software
+Foundation.
-This manual is far from complete, and we welcome informed contributions, be it
in the form of new chapters or insightful comments.
+A copy of the license is also available from the Free Software
+Foundation Web site at @url{http://www.gnu.org/licenses/gpl.html}.
address@hidden copying
-However, the website is experiencing a constant onslaught of sophisticated
link-spam entered manually by exploited workers solving puzzles and customizing
text. To limit this commercial defacement, we are strictly moderating comments
and have disallowed "normal" users from posting new content. However, this is
really only intended to keep the spam at bay. If you are a real user or
aspiring developer, please drop us a note (IRC, e-mail, contact form) with your
user profile ID number inclu [...]
address@hidden @bullet
address@hidden User Handbook of GNUnet
address@hidden
+* foo
address@hidden direntry
address@hidden
address@hidden User Handbook of GNUnet
address@hidden The GNUnet Developers
address@hidden
address@hidden
address@hidden 0pt plus 1filll
+Edition @value{EDITION} @*
address@hidden @*
address@hidden
address@hidden titlepage
address@hidden
-Español
address@hidden
address@hidden
***************************************************************************
address@hidden Top
address@hidden Introduction
+
+This book documents how to use the various Peer-to-Peer applications of the
+GNUnet system. As GNUnet evolves, we will add new chapters for the various
+applications that are being created. Comments and extensions are always
welcome.
+As with all documentation on this page, this is free documentation available
+under both the GPLv3+ or the GFDL at your choice (see copyright).
+
+This manual is far from complete, and we welcome informed contributions, be it
+in the form of new chapters or insightful comments.
+
+However, the website is experiencing a constant onslaught of sophisticated
+link-spam entered manually by exploited workers solving puzzles and customizing
+text. To limit this commercial defacement, we are strictly moderating comments
+and have disallowed "normal" users from posting new content. However, this is
+really only intended to keep the spam at bay. If you are a real user or
aspiring
+developer, please drop us a note (IRC, e-mail, contact form) with your user
+profile ID number included. We will then relax these restrictions on your
+account. We're sorry for this inconvenience; however, few people would want to
+read this site if 99% of it was advertisements for bogus websites.
address@hidden
-Français
address@hidden itemize
@settitle Tutorial: Using GNUnet
@c %**end of header
@@ -33,15 +74,6 @@ Français
This tutorial is supposed to give a first introduction for end-users trying to
do something "real" with GNUnet. Installation and configuration are
specifically outside of the scope of this tutorial. Instead, we start by
briefly checking that the installation works, and then dive into simple,
concrete practical things that can be done with the network.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Français
address@hidden itemize
@settitle Checking the Installation
@c %**end of header
@@ -104,16 +136,6 @@ You can click on "Traffic" to see information about the
amount of bandwidth your
You should now click on the Australian Aboriginal Flag. Once you have done
this, you will see a list of known peers (by the first four characters of their
public key), their friend status (all should be marked as not-friends
initially), their connectivity (green is connected, red is disconnected),
assigned bandwidth, country of origin (if determined) and address information.
If hardly any peers are listed and/or if there are very few peers with a green
light for connectivity, there is li [...]
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Français
address@hidden itemize
-
@multitable @columnfractions 0.333333333333333 0.333333333333333
0.333333333333333
@item Attachment
@@ -626,15 +648,6 @@ Size
This chapter documents the GNUnet file-sharing application. The original
file-sharing implementation for GNUnet was designed to provide
@strong{anonymous} file-sharing. However, over time, we have also added support
for non-anonymous file-sharing (which can provide better performance).
Anonymous and non-anonymous file-sharing are quite integrated in GNUnet and,
except for routing, share most of the concepts and implementation. There are
three primary file-sharing operations: publishing, [...]
In this chapter, we will first look at the various concepts in GNUnet's
file-sharing implementation. Then, we will discuss specifics as to how they
impact users that publish, search or download files.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle File-sharing: Concepts
@c %**end of header
@@ -710,15 +723,6 @@ Depending on the peer's configuration, GNUnet peers
migrate content between peer
When peers migrate content to other systems, the replication level of a block
is used to decide which blocks need to be migrated most urgently. GNUnet will
always push the block with the highest replication level into the network, and
then decrement the replication level by one. If all blocks reach replication
level zero, the selection is simply random.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle File-sharing: Publishing
@c %**end of header
@@ -760,15 +764,6 @@ Since it is much less efficient, this is strongly
discouraged for large files. W
The option @code{-n} may be used if the user fears that the file might be
found on his drive (assuming the computer comes under the control of an
adversary).@
When used with the @code{-n} flag, the user has a much better chance of
denying knowledge of the existence of the file, even if it is still (encrypted)
on the drive and the adversary is able to crack the encryption (e.g. by
guessing the keyword.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle File-sharing: Searching
@c %**end of header
@@ -806,15 +801,7 @@ as the first will match files shared under the keywords
"Das" or "Kapital" where
The argument passed to @code{-o} is the suggested filename (you may change it
to whatever you like).@
The @code{--} is followed by key for decrypting the file, the query for
searching the file, a checksum (in hexadecimal) finally the size of the file in
bytes.@
The second line contains the description of the file; here this is "The GNU
Public License" and the mime-type (see the options for gnunet-publish on how to
specify these).
address@hidden @bullet
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle File-sharing: Downloading
@c %**end of header
@@ -858,15 +845,6 @@ Español
Directories are shared just like ordinary files. If you download a directory
with @code{gnunet-download}, you can use @code{gnunet-directory} to list its
contents. The canonical extension for GNUnet directories when stored as files
in your local file-system is ".gnd". The contents of a directory are URIs and
meta data.@
The URIs contain all the information required by @code{gnunet-download} to
retrieve the file. The meta data typically includes the mime-type, description,
a filename and other meta information, and possibly even the full original file
(if it was small).
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle File-sharing: Namespace Management
@c %**end of header
@@ -918,15 +896,6 @@ The gnunet-pseudonym tool can be used to create pseudonyms
and to advertise name
An item of particular interest in the namespace advertisement is the ROOT.@
The ROOT is the identifier of a designated entry in the namespace. The idea
is that the ROOT can be used to advertise an entry point to the content of the
namespace.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle File-Sharing URIs
@c %**end of header
@@ -1027,15 +996,6 @@ Compatibility with DNS
For the initial configuration and population of your GNS installation, please
follow the GNS setup instructions. The remainder of this chapter will provide
some background on GNS and then describe how to use GNS in more detail.
Unlike DNS, GNS does not rely on central root zones or authorities. Instead
any user administers his own root and can can create arbitrary name value
mappings. Furthermore users can delegate resolution to other users' zones just
like DNS NS records do. Zones are uniquely identified via public keys and
resource records are signed using the corresponding public key. Delegation to
another user's zone is done using special PKEY records and petnames. A petname
is a name that can be freely cho [...]
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Maintaining your own Zones
@c %**end of header
@@ -1067,15 +1027,6 @@ To provide a simple example for editing your own zone,
suppose you have your own
Afterwards, you will be able to access your webpage under "www.gnu"(assuming
your webserver does not use virtual hosting, if it does, please read up on
setting up the GNS proxy).
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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Obtaining your Zone Key
@c %**end of header
@@ -1093,15 +1044,6 @@ You can usually get the hash of your public key using@
DC3SEECJORPHQNVRH965A6N74B1M37S721IG4RBQ15PJLLPJKUE0.
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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Adding Links to Other Zones
@c %**end of header
@@ -1120,15 +1062,6 @@ Suppose you have a friend who you call 'bob' who also
uses GNS. You can then del
Assuming Bob has an A record for his website under the name of www in his
zone, you can then access Bob's website under www.bob.gnu --- as well as any
(public) GNS record that Bob has in his zone by replacing www with the
respective name of the record in Bob's zone.
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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle The Three Local Zones of GNS
@c %**end of header
@@ -1173,15 +1106,6 @@ The private zone is a subzone (or subdomain in DNS
terms) of your master zone. I
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 this zone with other users' zones based on their PSEU records whenever
you resolve a name.
For example if you go to @address@hidden://www.bob.alice.dave.gnu/,
www.bob.alice.dave.gnu}}, GNS will try to import @code{bob} into your shorten
zone. Having obtained Bob's PKEY from @code{alice.dave.gnu}, GNS will lookup
the PSEU record for @code{+} in Bob's zone. If it exists and the specified
pseudonym is not taken, Bob's PKEY will be automatically added under that
pseudonym (i.e. "bob") into your shorten zone. From then on, Bob's webpage will
also be available for you as @address@hidden [...]
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle The ZKEY Top Level Domain in GNS
@c %**end of header
@@ -1190,15 +1114,6 @@ Español
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
key of a zone. Names in the .zkey TLD are then resolved by querying the
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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Resource Records in GNS
@c %**end of header
@@ -1352,15 +1267,6 @@ A DNS name
The resolver will expand the zone relative name if possible. Note that when
using MX records within GNS, the target mail server might still refuse to
accept e-mails to the resulting domain as the name might not match. GNS-enabled
mail 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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle The Virtual Public Network
@c %**end of header
@@ -1375,15 +1281,6 @@ The first thing to note about the GNUnet VPN is that it
is a public network. All
The VPN is currently only supported on GNU/Linux systems. Support for
operating systems that support TUN (such as FreeBSD) should be easy to add (or
might not even require any coding at all --- we just did not test this so far).
Support for other operating systems would require re-writing the code to create
virtual network interfaces and to intercept DNS requests.
The VPN does not provide good anonymity. While requests are routed over the
GNUnet network, other peers can directly see the source and destination of each
(encapsulated) IP packet. Finally, if you use the VPN to access Internet
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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Setting up an Exit node
@c %**end of header
@@ -1420,15 +1317,6 @@ The exit node configuration does currently not allow you
to restrict the Interne
Note that by running an exit node GNUnet will configure your kernel to perform
IP-forwarding (for IPv6) and NAT (for IPv4) so that the traffic from the
virtual interface can be routed to the Internet. In order to provide an
IPv6-exit, you need to have a subnet routed to your host's external network
interface and assign a subrange of that subnet to the GNUnet exit's TUN
interface.
When running a local service, you should make sure that the local service is
(also) bound to the IP address of your EXIT interface (i.e. 169.254.86.1). It
will NOT work if your local service is just bound to loopback. You may also
want to create a "VPN" record in your zone of the GNU Name System to make it
easy for others to access your service via a name instead of just the full
service descriptor. Note that the identifier you assign the service can serve
as a passphrase or shared secre [...]
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Fedora and the Firewall
@c %**end of header
@@ -1439,15 +1327,6 @@ Español
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 fine. However, for IPv6 the standard rules prohibit traffic from the
network range of the virtual interface created by the exit daemon to the local
IPv6 address of the same interface (which is essentially loopback traffic, so
you might suspect that a standard firewall would leave this traffic alone).
However, as somehow for IPv6 t [...]
Possible ways to fix this include disabling the firewall (do you have a good
reason for having it on?) or disabling the firewall at least for the GNUnet
exit interface (or the respective IPv4/IPv6 address range). The best way to
diagnose 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 @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@settitle Setting up VPN node for protocol translation and tunneling
@c %**end of header
@@ -1464,15 +1343,6 @@ The GNUnet VPN uses DNS-ALG to hijack your IP traffic.
Whenever an application r
For applications that do not use DNS, you can also manually create such a
mapping using the gnunet-vpn command-line tool. Here, you specfiy the desired
address family of the result (i.e. "-4"), and the intended target IP on the
Internet ("-i 131.159.74.67") and "gnunet-vpn" will tell you which IP address
in the range of your VPN tunnel was mapped.
gnunet-vpn can also be used to access "internal" services offered by GNUnet
nodes. So if you happen to know a peer and a service offered by that peer, you
can create an IP tunnel to that peer by specifying the peer's identity, service
name and protocol (--tcp or --udp) and you will again receive an IP address
that will terminate at the respective peer's service.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
@contents
@bye
--
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: user.texi: first fixes, copyrights.,
gnunet <=