GNUNET-REVOCATION(1) | General Commands Manual | GNUNET-REVOCATION(1) |
gnunet-revocation
—
revoke private keys (of egos) in GNUnet
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 ] |
gnunet-revocation
can be used to verify if
a key has been revoked, to create a revocation certificate for later
revocation, to instantly revoke a key and to use a pre-generated revocation
certificate to revoke a key. Upon successful revocation, all peers will be
informed about the invalidity of the key. As this is an expensive operation,
GNUnet requires the issuer of the revocation to perform an expensive
proof-of-work computation before they will be allowed to perform the
revocation. gnunet-revocation will perform this computation. The computation
can be performed ahead of time, with the resulting revocation certificate
being stored in a file for later "instant" use. gnunet-revocation
also makes is possible to resume the pre-calculation of a revocation ---
simply abort a running proof-of-work calculation with CTRL-C, and the
existing revocation certificate file will contain the status of the
computation. Note that performing a revocation proof-of-work is deliberately
VERY expensive. Depending on your CPU, the calculation can take days or
weeks.
-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
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).
Report bugs by using https://bugs.gnunet.org or by sending electronic mail to <gnunet-developers@gnu.org>.
March 15, 2012 | Debian |