[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated: start to fix the no
|
From: |
gnunet |
|
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated: start to fix the node -> menu errors |
|
Date: |
Tue, 02 May 2017 17:21:30 +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 3438849 start to fix the node -> menu errors
3438849 is described below
commit 3438849e5ec7843458bdc10cdc80fa82247f5199
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:58:25 2017 +0000
start to fix the node -> menu errors
---
Makefile | 5 ++++
developer.texi | 67 +++++++++++++++++++++++++++++------------------
gnunet.texi | 43 +++++++++++++++++++++++++++++++
installation.texi | 14 +++-------
philosophy.texi | 77 ++++++++++++++++++++++++++++++-------------------------
user.texi | 34 +++++++++---------------
6 files changed, 148 insertions(+), 92 deletions(-)
diff --git a/Makefile b/Makefile
index d8ab589..f291e9f 100644
--- a/Makefile
+++ b/Makefile
@@ -4,6 +4,11 @@ pdf:
html:
texi2html gnunet.texi
+info:
+ makeinfo --no-split gnunet.texi
+
+all: pdf html
+
.PHONY: clean
clean:
rm *.aux *.log *.toc *.pdf *.cp *.cps *.html
diff --git a/developer.texi b/developer.texi
index 843cf20..40c96ec 100644
--- a/developer.texi
+++ b/developer.texi
@@ -1,6 +1,6 @@
@c ***************************************************************************
address@hidden Top
address@hidden GNUnet Developer Handbook
address@hidden GNUnet Developer Handbook
address@hidden GNUnet Developer Handbook
This book is intended to be an introduction for programmers that want to
extend the GNUnet framework. GNUnet is more than a simple peer-to-peer
@@ -1770,13 +1770,14 @@ default level).
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 @code{GNUNET_FORCE_LOG=";;GNUNET_NETWORK_socket_select;;DEBUG"
-gnunet-arm -s} Start GNUnet process tree, allowing any logging calls from the
address@hidden
address@hidden";;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).
@item
address@hidden"transport.*;;.*send.*;;DEBUG/;;;;WARNING" gnunet-arm
--s} Start GNUnet process tree, allowing any logging calls from the components
address@hidden"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
has WARNING level.
@@ -2689,35 +2690,47 @@ which is created from contrib/defaults.conf).@ Each of
the services is having a
section starting by the service name between square brackets, for example:
"[arm]". The following options configure how ARM configures or interacts with
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".@
+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
-a service with "valgrind" or "gdb"@
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
-start this service when the peer is started.@
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
@@ -4283,15 +4296,19 @@ changing rapidly).
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.@ 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.
+
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.
+
@end table
To put this in perspective, if someone remembers the LHC Higgs boson results,
diff --git a/gnunet.texi b/gnunet.texi
index 9d3e76b..92d0f1e 100644
--- a/gnunet.texi
+++ b/gnunet.texi
@@ -43,6 +43,49 @@ Edition @value{EDITION} @*
@end titlepage
@contents
address@hidden
*********************************************************************
address@hidden Top
address@hidden GNUnet
address@hidden
*********************************************************************
+
+This document describes GNUnet version @value{VERSION}.
+
address@hidden
+
+* Philosophy:: About GNUnet
+* GNUnet Installation Handbook:: How to install GNUnet
+* Using GNUnet:: Using GNUnet
+* GNUnet Developer Handbook:: Developing GNUnet
+* GNU Free Documentation License:: The license of this manual.
+* GNU General Public License:: The license of this manual.
+* Concept Index:: Concepts.
+* Programming Index:: Data types, functions, and variables.
+
address@hidden
+ --- The Detailed Node Listing ---
+
+Philosophy
+
+* Copyright and Contributions::
+* Design Goals::
+* Security & Privacy::
+* Versatility::
+* Practicality::
+* Key Concepts::
+* Authentication::
+* Accounting to Encourage Resource Sharing::
+* Confidentiality::
+* Anonymity::
+* How GNUnet achieves Anonymity::
+* Deniability::
+* Peer Identities::
+* Zones in the GNU Name System (GNS Zones)::
+* Egos::
+* Backup of Identities and Egos::
+* Revocation::
+
address@hidden detailmenu
address@hidden menu
@c *********************************************************************
@include philosophy.texi
diff --git a/installation.texi b/installation.texi
index 5df13eb..f2af005 100644
--- a/installation.texi
+++ b/installation.texi
@@ -1,4 +1,4 @@
address@hidden Top
address@hidden GNUnet Installation Handbook
@chapter GNUnet Installation Handbook
This handbook describes how to install (build setup, compilation) and setup
@@ -525,14 +525,16 @@ $ sudo make install@
Choose one or more database backends@
@itemize @bullet
+
@item
-SQLite3 code{$ sudo apt-get install libsqlite3-dev}
+SQLite3 @code{$ sudo apt-get install libsqlite3-dev}
@item
MySQL @code{$ sudo apt-get install libmysqlclient-dev}
@item
PostgreSQL @code{$ sudo apt-get install libpq-dev postgresql}
+
@end itemize
@subsection Build GNUnet
@@ -1551,10 +1553,6 @@ Done!
@subsection Basic Installation for Fedora/PlanetLab nodes running Fedora 8 .
@c %**end of header
address@hidden Top
-
-
-
@strong{This documentation is outdated and not valid for GNUnet 0.10.0!}@
GNUnet installation on Fedora 8/Planetlab nodes can be done as following:
@@ -2764,10 +2762,6 @@ table here, it probably works.
@subsection Configuring the datacache
@c %**end of header
address@hidden Top
-
-
-
The datacache is what GNUnet uses for storing temporary data. This data is
expected to be wiped completely each time GNUnet is restarted (or the system
is rebooted).
diff --git a/philosophy.texi b/philosophy.texi
index 0a232fc..60ab3c8 100644
--- a/philosophy.texi
+++ b/philosophy.texi
@@ -1,6 +1,7 @@
@c ***************************************************************************
@node Philosophy
@chapter Philosophy
+
The foremost goal of the GNUnet project is to become a widely used,
reliable, open, non-discriminating, egalitarian, unfettered and
censorship-resistant system of free information exchange.
@@ -13,10 +14,32 @@ another file-sharing network. The plan is to offer many
other services
and in particular to serve as a development platform for the next
generation of decentralized Internet protocols.
address@hidden
+
+* Copyright and Contributions::
+* Design Goals::
+* Security & Privacy::
+* Versatility::
+* Practicality::
+* Key Concepts::
+* Authentication::
+* Accounting to Encourage Resource Sharing::
+* Confidentiality::
+* Anonymity::
+* How GNUnet achieves Anonymity::
+* Deniability::
+* Peer Identities::
+* Zones in the GNU Name System (GNS Zones)::
+* Egos::
+* Backup of Identities and Egos::
+* Revocation::
+
address@hidden menu
+
@c ***************************************************************************
@node Copyright and Contributions
address@hidden Copyright and Contributions
address@hidden %**end of header
address@hidden Copyright and Contributions
+
GNUnet is a @uref{http://www.gnu.org/, GNU} package. All code contributions
must thus be put under the
@@ -52,8 +75,7 @@ section, please do let us know.
@c ***************************************************************************
@node Design Goals
address@hidden Design Goals
address@hidden %**end of header
address@hidden Design Goals
The foremost goal of the GNUnet project is to become a widely used, reliable,
open, non-discriminating, egalitarian, unfettered and censorship-resistant
@@ -67,8 +89,7 @@ services and in particular to serve as a development platform
for the
next generation of decentralized Internet protocols.
@node Security & Privacy
address@hidden Security & Privacy
address@hidden %**end of header
address@hidden Security & Privacy
GNUnet's primary design goals are to protect the privacy of its users and to
guard itself against attacks or abuse. GNUnet does not have any mechanisms
@@ -77,8 +98,7 @@ it as hard as possible to find out what is happening on the
network or to
disrupt operations.
@node Versatility
address@hidden Versatility
address@hidden %**end of header
address@hidden Versatility
We call GNUnet a peer-to-peer framework because we want to support many
different forms of peer-to-peer applications. GNUnet uses a plugin
@@ -98,8 +118,7 @@ not important, we could have just developed a dozen
stand-alone applications
and a few shared libraries.
@node Practicality
address@hidden Practicality
address@hidden %**end of header
address@hidden Practicality
GNUnet allows participants to trade various amounts of security in exchange
for increased efficiency. However, it is not possible for any user's security
@@ -130,8 +149,7 @@ TCP Nagle), a protocol that ensures that individual goals
never conflict
with the goals of the group is always preferable.
@node Key Concepts
address@hidden Key Concepts
address@hidden %**end of header
address@hidden Key Concepts
In this section, the fundamental concepts of GNUnet are explained. Most of
them are also described in our research papers. First, some of the concepts
@@ -139,8 +157,7 @@ used in the GNUnet framework are detailed. The second part
describes concepts
specific to anonymous file-sharing.
@node Authentication
address@hidden Authentication
address@hidden %**end of header
address@hidden Authentication
Almost all peer-to-peer communications in GNUnet are between mutually
authenticated peers. The authentication works by using ECDHE, that is a
@@ -179,8 +196,7 @@ advertisements.@
More details can be found in this paper.
@node Accounting to Encourage Resource Sharing
address@hidden Accounting to Encourage Resource Sharing
address@hidden %**end of header
address@hidden Accounting to Encourage Resource Sharing
Most distributed P2P networks suffer from a lack of defenses or precautions
against attacks in the form of freeloading. While the intentions of an
@@ -208,8 +224,7 @@ considered to have a surplus in contributions will not be
served if the
network load is high. More details can be found in this paper.
@node Confidentiality
address@hidden Confidentiality
address@hidden %**end of header
address@hidden Confidentiality
Adversaries outside of GNUnet are not supposed to know what kind of actions a
peer is involved in. Only the specific neighbor of a peer that is the
@@ -225,8 +240,7 @@ application-level protocols (see for example, deniability
and anonymity in
anonymous file sharing).
@node Anonymity
address@hidden Anonymity
address@hidden %**end of header
address@hidden Anonymity
Providing anonymity for users is the central goal for the anonymous
file-sharing application. Many other design decisions follow in the footsteps
@@ -245,8 +259,7 @@ to forego anonymity when this is not required. The
anonymity level of 0
allows GNUnet to use more efficient, non-anonymous routing.
@node How GNUnet achieves Anonymity
address@hidden How GNUnet achieves Anonymity
address@hidden %**end of header
address@hidden How GNUnet achieves Anonymity
Contrary to other designs, we do not believe that users achieve strong
anonymity just because their requests are obfuscated by a couple of
@@ -283,8 +296,7 @@ This increases the efficiency of the network as we can
indirect less under
higher load. More details can be found in this paper.
@node Deniability
address@hidden Deniability
address@hidden %**end of header
address@hidden Deniability
Even if the user that downloads data and the server that provides data are
anonymous, the intermediaries may still be targets. In particular, if the
@@ -303,8 +315,7 @@ by @command{gnunet-publish}, @command{gnunet-download},
@command{gnunet-search}
and @command{gnunet-gtk}). More details can be found here.
@node Peer Identities
address@hidden Peer Identities
address@hidden %**end of header
address@hidden Peer Identities
Peer identities are used to identify peers in the network and are unique for
each peer. The identity for a peer is simply its public key, which is
@@ -320,8 +331,7 @@ You can find your peer identity by running@
@command{gnunet-peerinfo -s}
@node Zones in the GNU Name System (GNS Zones)
address@hidden Zones in the GNU Name System (GNS Zones)
address@hidden %**end of header
address@hidden Zones in the GNU Name System (GNS Zones)
GNS zones are similar to those of DNS zones, but instead of a hierarchy of
authorities to governing their use, GNS zones are controlled by a private key.
@@ -341,8 +351,7 @@ key. And a user accessing a zone needs to somehow specify
the corresponding
public key first.
@node Egos
address@hidden Egos
address@hidden %**end of header
address@hidden Egos
Egos are your "identities" in GNUnet. Any user can assume multiple identities,
for example to separate his activities online. Egos can correspond to
@@ -368,9 +377,8 @@ These egos and their usage is descibed here.
Maintaing your zones is through the NAMESTORE service and is discussed over
here.
address@hidden Backup of Identities, Egos
address@hidden Backup of Identities, Egos
address@hidden %**end of header
address@hidden Backup of Identities and Egos
address@hidden Backup of Identities and Egos
One should always backup their files, especially in these SSD days (our
team has suffered 3 SSD crashes over a span of 2 weeks). Backing up peer
@@ -389,8 +397,7 @@ Note: All these files contain cryptographic keys and they
are stored without
any encryption. So it is advisable to backup encrypted copies of them.
@node Revocation
address@hidden Revocation
address@hidden %**end of header
address@hidden Revocation
Now, in the situation of an attacker gaining access to the private key of
one of your egos, the attacker can create records in the respective GNS zone
diff --git a/user.texi b/user.texi
index cfc488f..04dc210 100644
--- a/user.texi
+++ b/user.texi
@@ -1,5 +1,15 @@
address@hidden Top
address@hidden Introduction
address@hidden Using GNUnet
address@hidden Using GNUnet
address@hidden %**end of header
+
+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 Introduction
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
@@ -10,26 +20,6 @@ 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 Tutorial: Using GNUnet
address@hidden Tutorial: Using GNUnet
address@hidden %**end of header
-
-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.
-
@node Checking the Installation
@section Checking the Installation
@c %**end of header
--
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: start to fix the node -> menu errors,
gnunet <=