aboutsummaryrefslogtreecommitdiff
path: root/doc/handbook/chapters/user.texi
diff options
context:
space:
mode:
Diffstat (limited to 'doc/handbook/chapters/user.texi')
-rw-r--r--doc/handbook/chapters/user.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/handbook/chapters/user.texi b/doc/handbook/chapters/user.texi
index b5889891b..911d23526 100644
--- a/doc/handbook/chapters/user.texi
+++ b/doc/handbook/chapters/user.texi
@@ -109,7 +109,7 @@ rules - GO0T87F9BPMF8NKD5A54L2AH1T0GRML539TPFSRMCEA98182QD30
109@subsection The GNS Tab 109@subsection The GNS Tab
110 110
111 111
112Maintaing your zones is through the NAMESTORE service and is discussed 112Maintaining your zones is through the NAMESTORE service and is discussed
113here. You can manage your zone using @command{gnunet-identity} and 113here. You can manage your zone using @command{gnunet-identity} and
114@command{gnunet-namestore}, or most conveniently using 114@command{gnunet-namestore}, or most conveniently using
115@command{gnunet-namestore-gtk}. 115@command{gnunet-namestore-gtk}.
@@ -1633,7 +1633,7 @@ are BOXed up.
1633@subsubsection LEHO 1633@subsubsection LEHO
1634 1634
1635The LEgacy HOstname of a server. Some webservers expect a specific 1635The LEgacy HOstname of a server. Some webservers expect a specific
1636hostname to provide a service (virtiual hosting). Also SSL 1636hostname to provide a service (virtual hosting). Also SSL
1637certificates usually contain DNS names. To provide the expected 1637certificates usually contain DNS names. To provide the expected
1638legacy DNS name for a server, the LEHO record can be used. 1638legacy DNS name for a server, the LEHO record can be used.
1639To mitigate the just mentioned issues the GNS proxy has to be used. 1639To mitigate the just mentioned issues the GNS proxy has to be used.
@@ -2404,7 +2404,7 @@ $ gnunet-peerinfo -s
2404 2404
2405A ROOMKEY gets entered in readable text form. The service will then hash the 2405A ROOMKEY gets entered in readable text form. The service will then hash the
2406entered ROOMKEY and use the result as shared secret for transmission through 2406entered ROOMKEY and use the result as shared secret for transmission through
2407the CADET submodule. You can also optionally leave out the '-r' paramter and 2407the CADET submodule. You can also optionally leave out the '-r' parameter and
2408the ROOMKEY to use the zeroed hash instead. 2408the ROOMKEY to use the zeroed hash instead.
2409 2409
2410If no IDENTITY is provided you will not send any name to others, you will be 2410If no IDENTITY is provided you will not send any name to others, you will be
@@ -2478,7 +2478,7 @@ $ gnunet-messenger [-e IDENTITY] -d PEERIDENTITY -r ROOMKEY -p
2478@end example 2478@end example
2479 2479
2480Notice that you can only send such encrypted messages to members who use an ego 2480Notice that you can only send such encrypted messages to members who use an ego
2481which is not publically known as the anonymous ego to ensure transparency. If 2481which is not publicly known as the anonymous ego to ensure transparency. If
2482any user could decrypt these messages they would not be private. So as receiver 2482any user could decrypt these messages they would not be private. So as receiver
2483of such messages the IDENTITY is required and it has to match a local ego. 2483of such messages the IDENTITY is required and it has to match a local ego.
2484 2484