GNUNET-IDENTITY(1)

πŸ“¦
version 0.27.0 Β· 2 versions
  • 0.27.0 Β· alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking (latest)
  • 0.15.3 Β· ubuntu jammy
, in alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

GNUNET-IDENTITY πŸ’…

okay bestie, welcome to the gnunet-identity page from the General Commands Manual β€” she's a whole icon and she's about to make egos make sense, fr fr.


✨ NAME ✨

gnunet-identity β€” maintain (create, delete or list) or perform actions with egos πŸŽ€


🌸 SYNOPSIS 🌸

gnunet-identity [-C NAME | --create=NAME] [-D NAME | --delete=NAME]
                [-d | --display] [-e NAME | --ego=NAME] [-h | --help]
                [-k PUBLIC_KEY | --key=PUBLIC_KEY] [-m | --monitor]
                [-p | --private-keys] [-q | --quiet]
                [-R MESSAGE | --read=MESSAGE] [-V | --verbose]
                [-W MESSAGE | --write=MESSAGE] [-X | --eddsa]

πŸ’– DESCRIPTION πŸ’–

so gnunet-identity is the tool for managing egos. and no, an ego here is not your ex β€” an ego is the persona that controls a namespace. it is identical to a public-private ECC key pair. iconic behavior honestly.

she can do a bunch of stuff, like:

  • list all of the egos that were created locally
  • create new egos
  • delete existing egos β€” and heads up bestie, when you delete one, the namespace will continue to exist, but it will be impossible to add additional data to it πŸ’€

and that's not all!! you can also encrypt and decrypt messages (arbitrary strings, so like, whatever you want) using a given public key (for encryption) or an ego (for decryption). she's multifaceted, we love that.

one thing you gotta know: creating a new ego requires using the -C option together with an identifier (name) that is to be used for the new ego. and this identifier is only used locally for this peer and not shared with other peers. so it's your little secret, iykyk 🀫

the options are as follows:

  • -C NAME, --create=NAME β€” creates a new ego with the given NAME. brand new baby ego, slay πŸ¦‹
  • -D NAME, --delete=NAME β€” delete the ego with the given NAME. bye bestie πŸ’”
  • -d, --display β€” display all of our egos. the full roster, no cap.
  • -e NAME, --ego=NAME β€” perform "set" operation with the respective ego, or restrict "display" operation to the respective ego. one ego, main character energy only πŸ‘‘
  • -h, --help β€” print the help page. she's helpful like that 🫢
  • -k PUBLIC_KEY, --key=PUBLIC_KEY β€” the public key to use for a message recipient. use together with -W. the recipient can obtain the desired ego's public key using the "display" operation. pass it along bestie πŸ’Œ
  • -m, --monitor β€” 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>". okay so it's literally livestreaming your egos πŸ“Ί
  • -p, --private-keys β€” 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. three columns of pure drama πŸ“Š
  • -q, --quiet β€” be quiet, in particular outputs only the public key when listing egos. shhh, minimal vibes ✨
  • -R MESSAGE, --read=MESSAGE β€” decrypt (read) a message using the respective ego private key. use together with -e. the message consists of an ephemeral key and the ciphertext, separated by a dot. such messages can be created with -W. reading is fundamental, bestie πŸ“–
  • -V, --verbose β€” be verbose, in particular outputs the public key of freshly created egos. she's chatty and we love her πŸ—£οΈ
  • -W MESSAGE, --write=MESSAGE β€” encrypt (write) the given message for the identity given with -k. the output contains an ephemeral message public key and the message separated by a dot. the entire line needs to be transferred to the recipient, who can use -R to decrypt the message. the entire line, do not be out here copy-pasting half of it πŸ™ˆ
  • -X, --eddsa β€” use EdDSA instead of ECDSA. switching it up πŸ’…

πŸŽ€ FILES πŸŽ€

  • ~/.local/share/gnunet/identity/egos β€” directory where the egos are stored by default. that's where all your egos live, rent free 🏠

🌈 SEE ALSO 🌈

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

info gnunet

should give you access to the complete handbook,

info gnunet-c-tutorial

will give you access to a tutorial for developers.

depending on your installation, this information is also available in gnunet(7) and gnunet-c-tutorial(7). go read, bestie, knowledge is the vibe check πŸ“šβœ¨


πŸ’€ BUGS πŸ’€

found a bug? report bugs by using https://bugs.gnunet.org or by sending electronic mail to ⟨gnunet-developers@gnu.org⟩. don't suffer in silence, tell the devs 🫢


and that's the whole page bestie!! this version came from Debian, dated September 5, 2013, under the title GNUNET-IDENTITY(1). she's vintage but she ate and left no crumbs πŸ’…βœ¨πŸŽ€ go create some egos, periodt πŸ’–