|GNUNET-IDENTITY(1)||General Commands Manual||GNUNET-IDENTITY(1)|
gnunet-identityis a tool for managing egos. An ego is the persona that controls a namespace. It is identical to a public-private ECC key pair.
gnunet-identity can be used to list all of the egos that were created locally, to create new egos, and to delete existing egos (the namespace will continue to exist, but it will be impossible to add additional data to it).
Creating a new ego requires using the
option together with an identifier (name) that is to be used for the new
ego. This identifier is only used locally for this peer and not shared with
other peers. The options are as follows:
- Creates a new ego with the given NAME.
- Delete the ego with the given NAME.
- Display all of our egos.
- Perform "set" operation with the respective ego or restrict "display" operation to the respective ego.
- Print the help page.
- Run in monitor mode, listing all ouf our egos until CTRL-C is pressed. Each ego is listed together with a unique pointer value; if egos are renamed, that pointer value remains the same, if egos are deleted, they are listed one more time with a name of "<null>".
- Print the private keys (in Crockford Base32 encoding), and not just the public keys. The second column shows the public key, the third column shows the private key.
- Be quiet, in particular outputs only the public key when listing egos.
- Perform "set" operation for the specified
SUBSYSTEM with the respective ego. Needs to be used
together with option
-e. After this, the given SUBSYSTEM will use the ego with the specified NAME. This will fail if NAME does not yet exist.
- Be verbose, in particular outputs the public key of freshly created egos.
FILES¶~/.local/share/gnunet/identity/egos Directory where the egos are stored by default
SEE ALSO¶gnunet-gns(1), gnunet-namestore(1)
The full documentation for gnunet is maintained as a Texinfo manual. If the info(1) and gnunet programs are properly installed at your site, the command
should give you access to the complete handbook,
will give you access to a tutorial for developers.
BUGS¶Report bugs by using https://bugs.gnunet.org or by sending electronic mail to <firstname.lastname@example.org>.
|September 5, 2013||Linux 4.19.0-14-amd64|