GNUNET-REVOCATION(1)

✨ GNUNET-REVOCATION ✨

okay bestie, welcome to the gnunet-revocation(1) page — yes it's from the General Commands Manual and yes it's about to be your new obsession 💅

🌸 NAME 🌸

gnunet-revocation — revoke private keys (of egos) in GNUnet 🦋

🎀 SYNOPSIS 🎀

gnunet-revocation [-t KEY | --test=KEY] [-e EPOCHS | --epochs=EPOCHS]
                  [-R NAME | --revoke=NAME] [-p | --perform]
                  [-f NAME | --filename=NAME]
                  [-c FILENAME, --config=FILENAME] [-h | --help]
                  [-L LOGLEVEL | --loglevel=LOGLEVEL] [-v | --version]

💖 DESCRIPTION 💖

so gnunet-revocation is literally the whole toolkit for key revocation. it can check if a key has already been revoked, it can make you a revocation certificate to keep for later, it can revoke a key instantly, and it can take a certificate you already generated and use it to revoke a key. the second a revocation goes through, all peers get told the key is invalid — no cap, the whole network finds out. 👑

but here's the tea: this is an expensive operation. GNUnet makes the issuer of the revocation do an expensive proof-of-work computation before they're even allowed to revoke. gnunet-revocation does that math for you. you can also do the computation ahead of time and stash the resulting revocation certificate in a file for later "instant" use. and get this — you can even resume a pre-calculation. just abort a running proof-of-work with CTRL-C and the revocation certificate file you've got will hold the status of the computation, so nothing is wasted. 🫶

⚠️ okay real talk: a revocation proof-of-work is deliberately VERY expensive. depending on your CPU, the calculation can take days or weeks. 😭 plan accordingly, hydrate, etc.

• -t KEY, --test=KEY — vibe-check whether the given KEY has been revoked. heads up: the key has to be an ASCII-encoded public key. required. 🔍
• -e EPOCHS, --epochs=EPOCHS — how many epochs the revocation should stay valid for (default: 1) ⏳
• -R NAME, --revoke=NAME — calculate or perform the revocation for the ego with the given NAME 🪪
• -p, --perform — actually DO the revocation as soon as possible. like, don't just generate a certificate and leave it sitting there — use it. you must pass this if you genuinely want the revocation performed. no -p, no revocation, periodt. 🔥
• -f NAME, --filename=NAME — use NAME as the name of the file that's gonna hold the revocation certificate. intermediate computation results get stored here too, plus the final certificate at the end. when you pair it with -p, this file gets inspected to see if it already has a valid certificate for instant revocation — and if it does, the revocation can happen instantly. also: if the given file contains anything (a valid certificate, with or without the completed proof-of-work), there's no need to supply the "-R" option, and no need to still have the private key of the ego to perform the revocation. iconic. 🎀
• -c FILENAME, --config=FILENAME — use the configuration file FILENAME ⚙️
• -h, --help — print the short help on options 📖
• -L LOGLEVEL, --loglevel=LOGLEVEL — use LOGLEVEL for logging. valid values are DEBUG, INFO, WARNING and ERROR. 🪵
• -v, --version — print the GNUnet version number 🔢

🦋 SEE ALSO 🦋

the full documentation for gnunet lives as a Texinfo manual. if info(1) and the gnunet programs are properly installed at your site, this command

info gnunet

should give you access to the complete handbook, and

info gnunet-c-tutorial

will give you access to a tutorial for developers. depending on your installation, this info is also available in gnunet(7) and gnunet-c-tutorial(7). go read, bestie, it's giving educational 📚

🐛 BUGS 🐛

found a bug? report it by using https://bugs.gnunet.org or by sending electronic mail to ⟨gnunet-developers@gnu.org⟩. the devs wanna hear from you fr fr 💌

and that's the page!! 🎀 this one shipped under Debian, dated March 15, 2012, and it's page GNUNET-REVOCATION(1) of the manual — go revoke something responsibly, mwah 💖✨🦋