1 .TH GNUNET\-ECC 1 "June 5, 2017" "GNUnet"
4 gnunet\-ecc \- manipulate GNUnet ECC key files
8 .RI [ options ] FILENAME
12 \fBgnunet\-ecc\fP can be used to create an ECC private key and to
13 print the corresponding public key. You must specify a filename
14 containing an ECC private key in GNUnet format as an argument. If the
15 file does not exist, gnunet\-ecc will create a key. This may then
16 take a while. If the option \-p is given, the corresponding public
17 key will be printed to the console.
20 .IP "\-g COUNT, \-\-generate-keys=COUNT"
21 Create COUNT public-private key pairs and write them to FILENAME.
22 Used for creating a file for testing.
23 .IP "\-p, \-\-print-public-key"
24 Print the corresponding public key to stdout. This is the value used
25 for PKEY records in GNS.
26 .IP "\-P, \-\-print-private-key"
27 Print the corresponding private key to stdout. This is the value used
28 for PKEY records in GNS.
29 .IP "\-x, \-\-print-hex"
30 Print the corresponding public key to stdout in HEX format. Useful
31 for comparing to Ed25519 keys in X.509 tools.
32 .IP "\-c FILENAME, \-\-config=FILENAME"
33 Use the configuration file FILENAME.
35 Print short help on options.
36 .IP "\-L LOGLEVEL, \-\-loglevel=LOGLEVEL"
37 Use LOGLEVEL for logging. Valid values are DEBUG, INFO, WARNING and
39 .IP "\-v, \-\-version"
40 Print GNUnet version number.
44 Report bugs by using Mantis <https://bugs.gnunet.org/> or by sending
45 electronic mail to <gnunet\-developers@gnu.org>
47 The full documentation for
49 is maintained as a Texinfo manual. If the
53 programs are properly installed at your site, the command
57 should give you access to the complete handbook,
59 .B info gnunet-c-tutorial
61 will give you access to a tutorial for developers.
63 Depending on your installation, this information is also
65 \fBgnunet\fP(7) and \fBgnunet-c-tutorial\fP(7).