commit 77a011d421b3d0c89f1c7006c00280ba6c7c4199
parent 6ef3761fe695eb3ec38a6e7e6a23f1517c6ed279
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Tue, 6 Aug 2024 10:53:24 +0200
remove mentions of gnunet-peerinfo
Diffstat:
4 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/developers/apis/transport.rst b/developers/apis/transport.rst
@@ -567,7 +567,7 @@ GNU/Linux you must:
interface (*hci0*) and the other which will use the second interface
(*hci1*)). Let's name them *peer1.conf* and *peer2.conf*.
-- run *gnunet-peerinfo -c peerX.conf -s* in order to generate the peers
+- run *gnunet-core -c peerX.conf -i* in order to generate the peers
private keys. The **X** must be replace with 1 or 2.
- run *gnunet-arm -c peerX.conf -s -i=transport* in order to start the
@@ -575,7 +575,7 @@ GNU/Linux you must:
transport plugins list if the Bluetooth transport service doesn't
start.)
-- run *gnunet-peerinfo -c peer1.conf -s* to get the first peer's ID. If
+- run *gnunet-core -c peer1.conf -i* to get the first peer's ID. If
you already know your peer ID (you saved it from the first command),
this can be skipped.
diff --git a/developers/tutorial.rst b/developers/tutorial.rst
@@ -103,7 +103,7 @@ to interact with it. For example, you can run:
.. code-block:: text
- $ gnunet-peerinfo -s
+ $ gnunet-core -i
to obtain the public key of your peer.
@@ -202,10 +202,10 @@ Now, generate the 2nd peer's private key:
.. code-block:: text
- $ gnunet-peerinfo -s -c peer2.conf
+ $ gnunet-core -i -c peer2.conf
This may take a while, generate entropy using your keyboard or mouse as
-needed. Also, make sure the output is different from the gnunet-peerinfo
+needed. Also, make sure the output is different from the gnunet-core
output for the first peer (otherwise you made an error in the
configuration).
@@ -275,10 +275,10 @@ should:
``gnunet-arm -c peer2.conf -s``
- Get ``HELLO`` message of the first peer running
- ``gnunet-peerinfo -c peer1.conf -g``
+ ``gnunet-core -c peer1.conf --export-hello``
- Give the output to the second peer by running
- ``gnunet-peerinfo -c peer2.conf -p '<output>'``
+ ``gnunet-core -c peer2.conf --import-hello '<output>'``
Check that they are connected using ``gnunet-core -c peer1.conf``, which
should give you the other peer's peer identity:
diff --git a/users/messenger.rst b/users/messenger.rst
@@ -56,11 +56,11 @@ key to sign your messages with.
$ gnunet-messenger [-e IDENTITY] -d PEERIDENTITY -r ROOMKEY
A PEERIDENTITY gets entered in encoded form. You can get your own peer
-ID by using the ``gnunet-peerinfo`` command:
+ID by using the ``gnunet-core`` command:
::
- $ gnunet-peerinfo -s
+ $ gnunet-core -i
A ROOMKEY gets entered in readable text form. The service will then hash
the entered ROOMKEY and use the result as shared secret for transmission
diff --git a/users/subsystems.rst b/users/subsystems.rst
@@ -410,7 +410,7 @@ to store and exchange peer addresses. GNUnet provides several methods
for peers to obtain this information:
- out-of-band exchange of HELLO messages (manually, using for example
- gnunet-peerinfo)
+ gnunet-core)
- HELLO messages shipped with GNUnet (automatic with distribution)
