diff options
author | Christian Grothoff <christian@grothoff.org> | 2021-04-24 00:02:25 +0200 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2021-04-24 00:02:25 +0200 |
commit | 8d48dbafe69193f8a23765154be1f7db851bfa1c (patch) | |
tree | 4f75a5809ecec95b178948586ccd76b2ef4ba2e3 /doc | |
parent | f630c5a675ca37467b5fba9a3dd41044381ac6ce (diff) | |
download | gnunet-8d48dbafe69193f8a23765154be1f7db851bfa1c.tar.gz gnunet-8d48dbafe69193f8a23765154be1f7db851bfa1c.zip |
-fix typos
Diffstat (limited to 'doc')
-rw-r--r-- | doc/handbook/chapters/developer.texi | 30 | ||||
-rw-r--r-- | doc/handbook/chapters/installation.texi | 8 | ||||
-rw-r--r-- | doc/handbook/chapters/keyconcepts.texi | 2 | ||||
-rw-r--r-- | doc/handbook/chapters/philosophy.texi | 2 | ||||
-rw-r--r-- | doc/handbook/chapters/preface.texi | 4 | ||||
-rw-r--r-- | doc/handbook/chapters/user.texi | 8 | ||||
-rw-r--r-- | doc/tutorial/tutorial.texi | 12 |
7 files changed, 33 insertions, 33 deletions
diff --git a/doc/handbook/chapters/developer.texi b/doc/handbook/chapters/developer.texi index 9bb74c3de..e7b88a39f 100644 --- a/doc/handbook/chapters/developer.texi +++ b/doc/handbook/chapters/developer.texi | |||
@@ -2305,7 +2305,7 @@ for new developers): | |||
2305 | @itemize @bullet | 2305 | @itemize @bullet |
2306 | @item logging (common_logging.c) | 2306 | @item logging (common_logging.c) |
2307 | @item memory allocation (common_allocation.c) | 2307 | @item memory allocation (common_allocation.c) |
2308 | @item endianess conversion (common_endian.c) | 2308 | @item endianness conversion (common_endian.c) |
2309 | @item internationalization (common_gettext.c) | 2309 | @item internationalization (common_gettext.c) |
2310 | @item String manipulation (string.c) | 2310 | @item String manipulation (string.c) |
2311 | @item file access (disk.c) | 2311 | @item file access (disk.c) |
@@ -4287,7 +4287,7 @@ which will warn you if you don't have the necessary libraries. | |||
4287 | @c work!@ Finally you just have to be sure that you have the correct drivers | 4287 | @c work!@ Finally you just have to be sure that you have the correct drivers |
4288 | @c for your Bluetooth device installed and that your device is on and in a | 4288 | @c for your Bluetooth device installed and that your device is on and in a |
4289 | @c discoverable mode. The Windows Bluetooth Stack supports only the RFCOMM | 4289 | @c discoverable mode. The Windows Bluetooth Stack supports only the RFCOMM |
4290 | @c protocol so we cannot turn on your device programatically! | 4290 | @c protocol so we cannot turn on your device programmatically! |
4291 | 4291 | ||
4292 | @c FIXME: Change to unique title | 4292 | @c FIXME: Change to unique title |
4293 | @node How does it work2? | 4293 | @node How does it work2? |
@@ -4638,7 +4638,7 @@ simply use the socket. | |||
4638 | @c implementation follows the same principles as the GNU/Linux one: | 4638 | @c implementation follows the same principles as the GNU/Linux one: |
4639 | 4639 | ||
4640 | @c @itemize @bullet | 4640 | @c @itemize @bullet |
4641 | @c @item It has a initalization part where it initializes the | 4641 | @c @item It has a initialization part where it initializes the |
4642 | @c Windows Sockets, creates a RFCOMM socket which will be binded and switched | 4642 | @c Windows Sockets, creates a RFCOMM socket which will be binded and switched |
4643 | @c to the listening mode and registers a SDP service. In the Microsoft | 4643 | @c to the listening mode and registers a SDP service. In the Microsoft |
4644 | @c Bluetooth API there are two ways to work with the SDP: | 4644 | @c Bluetooth API there are two ways to work with the SDP: |
@@ -5023,7 +5023,7 @@ key of the other peer | |||
5023 | ephemeral key of the other peer, but we are waiting for the other peer to | 5023 | ephemeral key of the other peer, but we are waiting for the other peer to |
5024 | confirm it's authenticity (ability to decode) via challenge-response. | 5024 | confirm it's authenticity (ability to decode) via challenge-response. |
5025 | @item @code{KX_STATE_UP} The connection is fully up from the point of | 5025 | @item @code{KX_STATE_UP} The connection is fully up from the point of |
5026 | view of the sender (now performing keep-alives) | 5026 | view of the sender (now performing keep-alive) |
5027 | @item @code{KX_STATE_REKEY_SENT} The sender has initiated a rekeying | 5027 | @item @code{KX_STATE_REKEY_SENT} The sender has initiated a rekeying |
5028 | operation; the other peer has so far failed to confirm a working | 5028 | operation; the other peer has so far failed to confirm a working |
5029 | connection using the new ephemeral key | 5029 | connection using the new ephemeral key |
@@ -5653,7 +5653,7 @@ download. The client component is basically a HTTP client | |||
5653 | (based on libcurl) which can download hostlists from one or more websites. | 5653 | (based on libcurl) which can download hostlists from one or more websites. |
5654 | The hostlist format is a binary blob containing a sequence of HELLO | 5654 | The hostlist format is a binary blob containing a sequence of HELLO |
5655 | messages. Note that any HTTP server can theoretically serve a hostlist, | 5655 | messages. Note that any HTTP server can theoretically serve a hostlist, |
5656 | the build-in hostlist server makes it simply convenient to offer this | 5656 | the built-in hostlist server makes it simply convenient to offer this |
5657 | service. | 5657 | service. |
5658 | 5658 | ||
5659 | 5659 | ||
@@ -5895,7 +5895,7 @@ The size of the list of URLs is restricted, so if an additional server is | |||
5895 | added and the list is full, the URL with the worst quality ranking | 5895 | added and the list is full, the URL with the worst quality ranking |
5896 | (determined through successful downloads and number of HELLOs e.g.) is | 5896 | (determined through successful downloads and number of HELLOs e.g.) is |
5897 | discarded. During shutdown the list of URLs is saved to a file for | 5897 | discarded. During shutdown the list of URLs is saved to a file for |
5898 | persistance and loaded on startup. URLs from the configuration file are | 5898 | persistence and loaded on startup. URLs from the configuration file are |
5899 | never discarded. | 5899 | never discarded. |
5900 | 5900 | ||
5901 | @node Usage | 5901 | @node Usage |
@@ -6155,7 +6155,7 @@ To disconnect from NAMESTORE, clients use | |||
6155 | @code{GNUNET_NAMESTORE_disconnect} and specify the handle to disconnect. | 6155 | @code{GNUNET_NAMESTORE_disconnect} and specify the handle to disconnect. |
6156 | 6156 | ||
6157 | NAMESTORE internally uses the ECDSA private key to refer to zones. These | 6157 | NAMESTORE internally uses the ECDSA private key to refer to zones. These |
6158 | private keys can be obtained from the IDENTITY subsytem. | 6158 | private keys can be obtained from the IDENTITY subsystem. |
6159 | Here @emph{egos} @emph{can be used to refer to zones or the default ego | 6159 | Here @emph{egos} @emph{can be used to refer to zones or the default ego |
6160 | assigned to the GNS subsystem can be used to obtained the master zone's | 6160 | assigned to the GNS subsystem can be used to obtained the master zone's |
6161 | private key.} | 6161 | private key.} |
@@ -6811,7 +6811,7 @@ the client. | |||
6811 | 6811 | ||
6812 | 6812 | ||
6813 | 6813 | ||
6814 | Each listener also requires a seperate client connection. By sending the | 6814 | Each listener also requires a separate client connection. By sending the |
6815 | @code{GNUNET_SERVICE_SET_LISTEN} message, the client notifies the service | 6815 | @code{GNUNET_SERVICE_SET_LISTEN} message, the client notifies the service |
6816 | of the application id and operation type it is interested in. A client | 6816 | of the application id and operation type it is interested in. A client |
6817 | rejects an incoming request by sending @code{GNUNET_SERVICE_SET_REJECT} | 6817 | rejects an incoming request by sending @code{GNUNET_SERVICE_SET_REJECT} |
@@ -7147,7 +7147,7 @@ the client. | |||
7147 | @node Listeners for Intersection | 7147 | @node Listeners for Intersection |
7148 | @subsubsection Listeners for Intersection | 7148 | @subsubsection Listeners for Intersection |
7149 | 7149 | ||
7150 | Each listener also requires a seperate client connection. By sending the | 7150 | Each listener also requires a separate client connection. By sending the |
7151 | @code{GNUNET_SERVICE_SETI_LISTEN} message, the client notifies the service | 7151 | @code{GNUNET_SERVICE_SETI_LISTEN} message, the client notifies the service |
7152 | of the application id and operation type it is interested in. A client | 7152 | of the application id and operation type it is interested in. A client |
7153 | rejects an incoming request by sending @code{GNUNET_SERVICE_SETI_REJECT} | 7153 | rejects an incoming request by sending @code{GNUNET_SERVICE_SETI_REJECT} |
@@ -7409,7 +7409,7 @@ the client. | |||
7409 | @node Listeners for Union | 7409 | @node Listeners for Union |
7410 | @subsubsection Listeners for Union | 7410 | @subsubsection Listeners for Union |
7411 | 7411 | ||
7412 | Each listener also requires a seperate client connection. By sending the | 7412 | Each listener also requires a separate client connection. By sending the |
7413 | @code{GNUNET_SERVICE_SETU_LISTEN} message, the client notifies the service | 7413 | @code{GNUNET_SERVICE_SETU_LISTEN} message, the client notifies the service |
7414 | of the application id and operation type it is interested in. A client | 7414 | of the application id and operation type it is interested in. A client |
7415 | rejects an incoming request by sending @code{GNUNET_SERVICE_SETU_REJECT} | 7415 | rejects an incoming request by sending @code{GNUNET_SERVICE_SETU_REJECT} |
@@ -7832,7 +7832,7 @@ performance). | |||
7832 | Third, an optional Bloom filter can be specified to exclude known results; | 7832 | Third, an optional Bloom filter can be specified to exclude known results; |
7833 | replies that hash to the bits set in the Bloom filter are considered | 7833 | replies that hash to the bits set in the Bloom filter are considered |
7834 | invalid. False-positives can be eliminated by sending the same query | 7834 | invalid. False-positives can be eliminated by sending the same query |
7835 | again with a different Bloom filter mutator value, which parameterizes | 7835 | again with a different Bloom filter mutator value, which parametrizes |
7836 | the hash function that is used. | 7836 | the hash function that is used. |
7837 | Finally, an optional application-specific "eXtended query" (xquery) can | 7837 | Finally, an optional application-specific "eXtended query" (xquery) can |
7838 | be specified to further constrain the results. It is entirely up to | 7838 | be specified to further constrain the results. It is entirely up to |
@@ -9810,7 +9810,7 @@ properties designed for application level usage: | |||
9810 | @item MESSENGER allows detection for dropped messages by chaining them (messages | 9810 | @item MESSENGER allows detection for dropped messages by chaining them (messages |
9811 | refer to the last message by their hash) improving accountability | 9811 | refer to the last message by their hash) improving accountability |
9812 | @item MESSENGER allows requesting messages from other peers explicitly to ensure | 9812 | @item MESSENGER allows requesting messages from other peers explicitly to ensure |
9813 | availibility | 9813 | availability |
9814 | @item MESSENGER provides confidentiality by padding messages to few different | 9814 | @item MESSENGER provides confidentiality by padding messages to few different |
9815 | sizes (512 bytes, 4096 bytes, 32768 bytes and maximal message size from | 9815 | sizes (512 bytes, 4096 bytes, 32768 bytes and maximal message size from |
9816 | CADET) | 9816 | CADET) |
@@ -9825,13 +9825,13 @@ Also MESSENGER provides multiple features with privacy in mind: | |||
9825 | @itemize @bullet | 9825 | @itemize @bullet |
9826 | @item MESSENGER allows deleting messages from all peers in the group by the | 9826 | @item MESSENGER allows deleting messages from all peers in the group by the |
9827 | original sender (uses the MESSENGER provided verification) | 9827 | original sender (uses the MESSENGER provided verification) |
9828 | @item MESSENGER allows using the publically known anonymous ego instead of any | 9828 | @item MESSENGER allows using the publicly known anonymous ego instead of any |
9829 | unique identifying ego | 9829 | unique identifying ego |
9830 | @item MESSENGER allows your node to decide between acting as host of the used | 9830 | @item MESSENGER allows your node to decide between acting as host of the used |
9831 | messaging room (sharing your peer's identity with all nodes in the group) | 9831 | messaging room (sharing your peer's identity with all nodes in the group) |
9832 | or acting as guest (sharing your peer's identity only with the nodes you | 9832 | or acting as guest (sharing your peer's identity only with the nodes you |
9833 | explicitly open a connection to) | 9833 | explicitly open a connection to) |
9834 | @item MESSENGER handles members independantly of the peer's identity making | 9834 | @item MESSENGER handles members independently of the peer's identity making |
9835 | forwarded messages indistinguishable from directly received ones ( | 9835 | forwarded messages indistinguishable from directly received ones ( |
9836 | complicating the tracking of messages and identifying its origin) | 9836 | complicating the tracking of messages and identifying its origin) |
9837 | @item MESSENGER allows names of members being not unique (also names are | 9837 | @item MESSENGER allows names of members being not unique (also names are |
@@ -9977,7 +9977,7 @@ check for completion of a member session requires this information. | |||
9977 | 9977 | ||
9978 | A member session is a triple of the room key, the member ID and the public key | 9978 | A member session is a triple of the room key, the member ID and the public key |
9979 | of the member's ego. Member sessions allow that a member can change their ID or | 9979 | of the member's ego. Member sessions allow that a member can change their ID or |
9980 | their ego once at a time without loosing the ability to delete old messages or | 9980 | their ego once at a time without losing the ability to delete old messages or |
9981 | identifying the original sender of a message. On every change of ID or EGO a | 9981 | identifying the original sender of a message. On every change of ID or EGO a |
9982 | session will be marked as closed. So every session chain will only contain one | 9982 | session will be marked as closed. So every session chain will only contain one |
9983 | open session with the current ID and public key. | 9983 | open session with the current ID and public key. |
diff --git a/doc/handbook/chapters/installation.texi b/doc/handbook/chapters/installation.texi index 40a23e738..ad939b5b7 100644 --- a/doc/handbook/chapters/installation.texi +++ b/doc/handbook/chapters/installation.texi | |||
@@ -171,7 +171,7 @@ group. In addition the group @code{gnunetdns} may be needed (see below). | |||
171 | 171 | ||
172 | Create user @code{gnunet} who is member of the group @code{gnunet} | 172 | Create user @code{gnunet} who is member of the group @code{gnunet} |
173 | (automatically created) and specify a home directory where the GNUnet | 173 | (automatically created) and specify a home directory where the GNUnet |
174 | services will store persistant data such as information about peers. | 174 | services will store persistent data such as information about peers. |
175 | @example | 175 | @example |
176 | $ sudo useradd --system --home-dir /var/lib/gnunet --create-home gnunet | 176 | $ sudo useradd --system --home-dir /var/lib/gnunet --create-home gnunet |
177 | @end example | 177 | @end example |
@@ -431,7 +431,7 @@ For the @emph{multi-user setup} first the system services need to be started | |||
431 | as the system user, i.e. the user @code{gnunet} needs to execute | 431 | as the system user, i.e. the user @code{gnunet} needs to execute |
432 | @code{gnunet-arm -s}. This should be done by the system's init system. | 432 | @code{gnunet-arm -s}. This should be done by the system's init system. |
433 | Then the user who wants to start GNUnet applications has to run | 433 | Then the user who wants to start GNUnet applications has to run |
434 | @code{gnunet-arm -s} too. It is recommented to automate this, e.g. using | 434 | @code{gnunet-arm -s} too. It is recommended to automate this, e.g. using |
435 | the user's crontab. | 435 | the user's crontab. |
436 | 436 | ||
437 | @node gnunet-gtk | 437 | @node gnunet-gtk |
@@ -1369,7 +1369,7 @@ proxy forwards the HTTP request he receives with a certain URL to another | |||
1369 | webserver, here a GNUnet peer. | 1369 | webserver, here a GNUnet peer. |
1370 | 1370 | ||
1371 | So if you have a running Apache or nginx webserver you can configure it to | 1371 | So if you have a running Apache or nginx webserver you can configure it to |
1372 | be a GNUnet reverse proxy. Especially if you have a well-known webiste | 1372 | be a GNUnet reverse proxy. Especially if you have a well-known website |
1373 | this improves censorship resistance since it looks as normal surfing | 1373 | this improves censorship resistance since it looks as normal surfing |
1374 | behaviour. | 1374 | behaviour. |
1375 | 1375 | ||
@@ -2175,7 +2175,7 @@ Sane defaults should exist in your | |||
2175 | you could simply start without any configuration. If you want to | 2175 | you could simply start without any configuration. If you want to |
2176 | configure your peer later, you need to stop it before invoking the | 2176 | configure your peer later, you need to stop it before invoking the |
2177 | @code{gnunet-setup} tool to customize further and to test your | 2177 | @code{gnunet-setup} tool to customize further and to test your |
2178 | configuration (@code{gnunet-setup} has build-in test functions). | 2178 | configuration (@code{gnunet-setup} has built-in test functions). |
2179 | 2179 | ||
2180 | The most important option you might have to still set by hand is in | 2180 | The most important option you might have to still set by hand is in |
2181 | [PATHS]. Here, you use the option "GNUNET_HOME" to specify the path where | 2181 | [PATHS]. Here, you use the option "GNUNET_HOME" to specify the path where |
diff --git a/doc/handbook/chapters/keyconcepts.texi b/doc/handbook/chapters/keyconcepts.texi index f429997bf..49129acf5 100644 --- a/doc/handbook/chapters/keyconcepts.texi +++ b/doc/handbook/chapters/keyconcepts.texi | |||
@@ -242,7 +242,7 @@ against identification. | |||
242 | 242 | ||
243 | The messaging service allows the use of an anonymous ego for the signing and | 243 | The messaging service allows the use of an anonymous ego for the signing and |
244 | verification process of messages instead of a unique ego. This anonymous ego is | 244 | verification process of messages instead of a unique ego. This anonymous ego is |
245 | a publically known key pair which is shared between all peers in GNUnet. | 245 | a publicly known key pair which is shared between all peers in GNUnet. |
246 | 246 | ||
247 | Using this ego only ensures that individual messages alone can't identify its | 247 | Using this ego only ensures that individual messages alone can't identify its |
248 | sender inside of a messenger room. It should be clarified that the route of | 248 | sender inside of a messenger room. It should be clarified that the route of |
diff --git a/doc/handbook/chapters/philosophy.texi b/doc/handbook/chapters/philosophy.texi index 060871189..785a65e42 100644 --- a/doc/handbook/chapters/philosophy.texi +++ b/doc/handbook/chapters/philosophy.texi | |||
@@ -70,7 +70,7 @@ applications. | |||
70 | @node Practicality | 70 | @node Practicality |
71 | @section Practicality | 71 | @section Practicality |
72 | 72 | ||
73 | Whereever possible GNUnet allows the peer to adjust its operations and | 73 | Wherever possible GNUnet allows the peer to adjust its operations and |
74 | functionalities to specific use cases. A GNUnet peer running on a | 74 | functionalities to specific use cases. A GNUnet peer running on a |
75 | mobile device with limited battery for example might choose not to | 75 | mobile device with limited battery for example might choose not to |
76 | relay traffic for other participants. | 76 | relay traffic for other participants. |
diff --git a/doc/handbook/chapters/preface.texi b/doc/handbook/chapters/preface.texi index 62ced08a4..d1afdf756 100644 --- a/doc/handbook/chapters/preface.texi +++ b/doc/handbook/chapters/preface.texi | |||
@@ -85,7 +85,7 @@ book which explains GNUnet in the least complicated way to you. | |||
85 | 85 | ||
86 | Even when you don't want to or can't learn Texinfo, you can contribute. | 86 | Even when you don't want to or can't learn Texinfo, you can contribute. |
87 | Send us an Email or join our IRC chat room on freenode and talk with | 87 | Send us an Email or join our IRC chat room on freenode and talk with |
88 | us about the documentation (the prefered way to reach out is the | 88 | us about the documentation (the preferred way to reach out is the |
89 | mailinglist, since you can communicate with us without waiting on | 89 | mailinglist, since you can communicate with us without waiting on |
90 | someone in the chatroom). | 90 | someone in the chatroom). |
91 | One way or another you can help shape the understanding of GNUnet | 91 | One way or another you can help shape the understanding of GNUnet |
@@ -144,7 +144,7 @@ and privacy-preserving online payments. In 2015, the | |||
144 | @c XXX: but the correct version would lead to problems with | 144 | @c XXX: but the correct version would lead to problems with |
145 | @c XXX: some of our outputs and/or older versions of texinfo | 145 | @c XXX: some of our outputs and/or older versions of texinfo |
146 | @c XXX: and devices that display versions on consoles etc. | 146 | @c XXX: and devices that display versions on consoles etc. |
147 | @c XXX: This is why we keep the pEp until proven that p(tripple bar)p | 147 | @c XXX: This is why we keep the pEp until proven that p(triple bar)p |
148 | @c XXX: does not create broken outputs. | 148 | @c XXX: does not create broken outputs. |
149 | @uref{https://pep.foundation/, pretty Easy privacy} (pEp) project | 149 | @uref{https://pep.foundation/, pretty Easy privacy} (pEp) project |
150 | announced that they will use GNUnet as the technology for their | 150 | announced that they will use GNUnet as the technology for their |
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 | ||
112 | Maintaing your zones is through the NAMESTORE service and is discussed | 112 | Maintaining your zones is through the NAMESTORE service and is discussed |
113 | here. You can manage your zone using @command{gnunet-identity} and | 113 | here. 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 | ||
1635 | The LEgacy HOstname of a server. Some webservers expect a specific | 1635 | The LEgacy HOstname of a server. Some webservers expect a specific |
1636 | hostname to provide a service (virtiual hosting). Also SSL | 1636 | hostname to provide a service (virtual hosting). Also SSL |
1637 | certificates usually contain DNS names. To provide the expected | 1637 | certificates usually contain DNS names. To provide the expected |
1638 | legacy DNS name for a server, the LEHO record can be used. | 1638 | legacy DNS name for a server, the LEHO record can be used. |
1639 | To mitigate the just mentioned issues the GNS proxy has to be used. | 1639 | To mitigate the just mentioned issues the GNS proxy has to be used. |
@@ -2404,7 +2404,7 @@ $ gnunet-peerinfo -s | |||
2404 | 2404 | ||
2405 | A ROOMKEY gets entered in readable text form. The service will then hash the | 2405 | A ROOMKEY gets entered in readable text form. The service will then hash the |
2406 | entered ROOMKEY and use the result as shared secret for transmission through | 2406 | entered ROOMKEY and use the result as shared secret for transmission through |
2407 | the CADET submodule. You can also optionally leave out the '-r' paramter and | 2407 | the CADET submodule. You can also optionally leave out the '-r' parameter and |
2408 | the ROOMKEY to use the zeroed hash instead. | 2408 | the ROOMKEY to use the zeroed hash instead. |
2409 | 2409 | ||
2410 | If no IDENTITY is provided you will not send any name to others, you will be | 2410 | If 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 | ||
2480 | Notice that you can only send such encrypted messages to members who use an ego | 2480 | Notice that you can only send such encrypted messages to members who use an ego |
2481 | which is not publically known as the anonymous ego to ensure transparency. If | 2481 | which is not publicly known as the anonymous ego to ensure transparency. If |
2482 | any user could decrypt these messages they would not be private. So as receiver | 2482 | any user could decrypt these messages they would not be private. So as receiver |
2483 | of such messages the IDENTITY is required and it has to match a local ego. | 2483 | of such messages the IDENTITY is required and it has to match a local ego. |
2484 | 2484 | ||
diff --git a/doc/tutorial/tutorial.texi b/doc/tutorial/tutorial.texi index e1d70c492..0a011c0c8 100644 --- a/doc/tutorial/tutorial.texi +++ b/doc/tutorial/tutorial.texi | |||
@@ -282,7 +282,7 @@ Assuming all dependencies are installed, the following commands will | |||
282 | compile and install GNUnet in your home directory. You can specify the | 282 | compile and install GNUnet in your home directory. You can specify the |
283 | directory where GNUnet will be installed by changing the | 283 | directory where GNUnet will be installed by changing the |
284 | @code{--prefix} value when calling @command{./configure}. If | 284 | @code{--prefix} value when calling @command{./configure}. If |
285 | you do not specifiy a prefix, GNUnet is installed in the directory | 285 | you do not specify a prefix, GNUnet is installed in the directory |
286 | @file{/usr/local}. When developing new applications you may want | 286 | @file{/usr/local}. When developing new applications you may want |
287 | to enable verbose logging by adding @code{--enable-logging=verbose}: | 287 | to enable verbose logging by adding @code{--enable-logging=verbose}: |
288 | 288 | ||
@@ -940,7 +940,7 @@ with the service, a connection must be created: | |||
940 | As a result a @code{GNUNET\_MQ\_Handle} is returned | 940 | As a result a @code{GNUNET\_MQ\_Handle} is returned |
941 | which can to used henceforth to transmit messages to the service. | 941 | which can to used henceforth to transmit messages to the service. |
942 | The complete MQ API can be found in @file{gnunet\_mq\_lib.h}. | 942 | The complete MQ API can be found in @file{gnunet\_mq\_lib.h}. |
943 | The @code{hanlders} array in the example above is incomplete. | 943 | The @code{handlers} array in the example above is incomplete. |
944 | Here is where you will define which messages you expect to | 944 | Here is where you will define which messages you expect to |
945 | receive from the service, and which functions handle them. | 945 | receive from the service, and which functions handle them. |
946 | The @code{error\_cb} is a function that is to be called whenever | 946 | The @code{error\_cb} is a function that is to be called whenever |
@@ -1060,7 +1060,7 @@ functions, typically called @code{run}, @code{client\_connect\_cb} and | |||
1060 | @code{client\_disconnect\_cb} as well as an array of message handlers | 1060 | @code{client\_disconnect\_cb} as well as an array of message handlers |
1061 | that will be called for incoming messages from clients. | 1061 | that will be called for incoming messages from clients. |
1062 | 1062 | ||
1063 | A minimal version of the three central service funtions would look | 1063 | A minimal version of the three central service functions would look |
1064 | like this: | 1064 | like this: |
1065 | 1065 | ||
1066 | @example | 1066 | @example |
@@ -1093,7 +1093,7 @@ forget to call @code{GNUNET\_SERVICE\_client\_continue()}? | |||
1093 | @node Interacting directly with other Peers using the CORE Service | 1093 | @node Interacting directly with other Peers using the CORE Service |
1094 | @section Interacting directly with other Peers using the CORE Service | 1094 | @section Interacting directly with other Peers using the CORE Service |
1095 | 1095 | ||
1096 | FIXME: This section still needs to be updated to the lastest API! | 1096 | FIXME: This section still needs to be updated to the latest API! |
1097 | 1097 | ||
1098 | One of the most important services in GNUnet is the @code{CORE} service | 1098 | One of the most important services in GNUnet is the @code{CORE} service |
1099 | managing connections between peers and handling encryption between peers. | 1099 | managing connections between peers and handling encryption between peers. |
@@ -1349,7 +1349,7 @@ sent. This does not guarantee that the data is accessible to others peers, | |||
1349 | or even that is has been stored, only that the service has requested to | 1349 | or even that is has been stored, only that the service has requested to |
1350 | a neighboring peer the retransmission of the PUT request towards its final | 1350 | a neighboring peer the retransmission of the PUT request towards its final |
1351 | destination. Currently there is no feedback about whether or not the data | 1351 | destination. Currently there is no feedback about whether or not the data |
1352 | has been sucessfully stored or where it has been stored. In order to | 1352 | has been successfully stored or where it has been stored. In order to |
1353 | improve the availablilty of the data and to compensate for possible | 1353 | improve the availablilty of the data and to compensate for possible |
1354 | errors, peers leaving and other unfavorable events, just make several | 1354 | errors, peers leaving and other unfavorable events, just make several |
1355 | PUT requests! | 1355 | PUT requests! |
@@ -1504,7 +1504,7 @@ GET request, a PUT request or a response (a reply to a GET). | |||
1504 | Since the different events have different associated data, | 1504 | Since the different events have different associated data, |
1505 | the API gets 3 different callbacks (one for each message type) | 1505 | the API gets 3 different callbacks (one for each message type) |
1506 | and optional type and key parameters, to allow for filtering of | 1506 | and optional type and key parameters, to allow for filtering of |
1507 | messages. When an event happens, the appropiate callback is | 1507 | messages. When an event happens, the appropriate callback is |
1508 | called with all the information about the event. | 1508 | called with all the information about the event. |
1509 | 1509 | ||
1510 | @example | 1510 | @example |