d03ab969 |
1 | .\" -*-nroff-*- |
052b36d0 |
2 | .ie t \{\ |
8404fd75 |
3 | . if \n(.g \{\ |
4 | . fam P |
5 | . \} |
052b36d0 |
6 | . ds ss \s8\u |
7 | . ds se \d\s0 |
1476eebc |
8 | . ds us \s8\d |
9 | . ds ue \u\s0 |
8404fd75 |
10 | . ds *b \(*b |
052b36d0 |
11 | .\} |
12 | .el \{\ |
13 | . ds ss ^ |
14 | . ds se |
1476eebc |
15 | . ds us _ |
8404fd75 |
16 | . ds ue |
17 | . ds *b \fIbeta\fP |
052b36d0 |
18 | .\} |
d07dfe80 |
19 | .TH key 1 "5 June 1999" "Straylight/Edgeware" "Catacomb cryptographic library" |
d03ab969 |
20 | .SH NAME |
21 | key \- simple key management system |
22 | .SH SYNOPSIS |
23 | .B key |
24 | .RB [ \-k |
25 | .IR keyring ] |
26 | .I command |
27 | .PP |
28 | where |
29 | .I command |
30 | is one of: |
31 | .PP |
32 | .B add |
d07dfe80 |
33 | .RB [ \-lqrLS ] |
052b36d0 |
34 | .RB [ \-a |
35 | .IR alg ] |
36 | .RB [ \-b | \-B |
d03ab969 |
37 | .IR bits ] |
052b36d0 |
38 | .RB [ \-p |
39 | .IR param ] |
d07dfe80 |
40 | .RB [ \-R |
052b36d0 |
41 | .IR tag ] |
42 | .br |
43 | \h'8n' |
d03ab969 |
44 | .RB [ \-e |
45 | .IR expire ] |
052b36d0 |
46 | .RB [ \-t |
47 | .IR tag ] |
d03ab969 |
48 | .RB [ \-c |
49 | .IR comment ] |
eb31b00e |
50 | .RB [ \-C |
51 | .IR curve ] |
52 | .br |
53 | \h'8n' |
d03ab969 |
54 | .I type |
55 | .IR attr ... |
56 | .br |
57 | .B expire |
052b36d0 |
58 | .IR tag ... |
d03ab969 |
59 | .br |
60 | .B delete |
052b36d0 |
61 | .IR tag ... |
62 | .br |
63 | .B tag |
64 | .I tag |
65 | .RI [ new-tag ] |
66 | .br |
67 | .B comment |
68 | .I tag |
69 | .RI [ comment ] |
d03ab969 |
70 | .br |
71 | .B setattr |
052b36d0 |
72 | .I tag |
d03ab969 |
73 | .IR attr ... |
74 | .br |
052b36d0 |
75 | .B lock |
76 | .I qtag |
77 | .br |
78 | .B unlock |
79 | .I qtag |
80 | .br |
d03ab969 |
81 | .B list |
052b36d0 |
82 | .RB [ \-uqv ] |
83 | .RB [ \-f |
84 | .IR filter ] |
85 | .RI [ tag ...] |
86 | .br |
87 | .B fingerprint |
88 | .RB [ \-f |
89 | .IR filter ] |
b817bfc6 |
90 | .RB [ \-a |
91 | .IR hash ] |
052b36d0 |
92 | .RI [ tag ...] |
d03ab969 |
93 | .br |
94 | .B tidy |
95 | .br |
96 | .B extract |
052b36d0 |
97 | .RB [ \-f |
98 | .IR filter ] |
d03ab969 |
99 | .I file |
052b36d0 |
100 | .RI [ tag ...] |
d03ab969 |
101 | .br |
102 | .B merge |
103 | .I file |
104 | .SH DESCRIPTION |
105 | The |
106 | .B key |
107 | command performs useful operations on Catacomb keyring files. It |
108 | provides a number of subcommands, by which the various operations may be |
109 | carried out. |
110 | .SS "Global options" |
111 | Before the command name, |
112 | .I "global options" |
113 | may be given. The following global options are supported: |
114 | .TP |
d07dfe80 |
115 | .BR "\-h, \-\-help " [ \fIcommand ] |
d03ab969 |
116 | Writes a brief summary of |
117 | .BR key 's |
118 | various options to standard output, and |
d07dfe80 |
119 | returns a successful exit status. With a command name, gives help on |
120 | that command. |
d03ab969 |
121 | .TP |
122 | .B "\-v, \-\-version" |
123 | Writes the program's version number to standard output, and returns a |
124 | successful exit status. |
125 | .TP |
126 | .B "\-u, \-\-usage" |
127 | Writes a very terse command line summary to standard output, and returns |
128 | a successful exit status. |
129 | .TP |
c9e31e42 |
130 | .BI "\-k, \-\-keyring " file |
d03ab969 |
131 | Names the keyring file which |
132 | .B key |
133 | is to process. The default keyring, used if this option doesn't specify |
134 | one, is the file named |
135 | .B keyring |
136 | in the current directory. The keyring must be stored in a regular file: |
137 | pipes, sockets, devices etc. are not allowed. |
138 | The |
139 | .B key |
140 | program attempts to lock the keyring before accessing it, using |
141 | .BR fcntl (2) |
142 | locking. It will however time out after a short while (10 seconds) and |
143 | report a failure. |
144 | .SS Concepts |
145 | In addition to the actual key data itself, a Catacomb key has a number |
146 | of other pieces of information attached to it: |
147 | .TP |
052b36d0 |
148 | .B "keyid" |
149 | Every key has a 32-bit identifying number, written in hexadecimal. |
150 | Keyids are not actually related to the key contents: they're generated |
151 | randomly. Applications use keyids to refer to specific keys; users are |
152 | probably better off with tags and types. A |
d03ab969 |
153 | .I deleted |
154 | key cannot be looked up by keyid. |
155 | .TP |
052b36d0 |
156 | .B "tag" |
157 | A key's tag is a unique string which can be used by users and |
158 | applications to identify the key. Tag strings may not contain spaces, |
159 | colons or dots. A |
160 | .I deleted |
161 | key cannot be looked up by tag. Whenever a tag name is wanted, a hex |
162 | keyid or key type string can be given instead. |
163 | .TP |
164 | .B "type" |
d03ab969 |
165 | A key's type string describes what the key may be used for. The type |
166 | string is arbitrary, except that it may not contain whitespace |
052b36d0 |
167 | characters, dots or colons. Applications use key types to obtain an |
168 | arbitrary but suitable key for some purpose. An |
d03ab969 |
169 | .I expired |
052b36d0 |
170 | key cannot be looked up by type, but may be looked up by keyid or tag. |
171 | .TP |
172 | .B "key encoding" |
173 | There are a number of different ways in which keys can be represented, |
174 | according to the uses to which the key will be put. Most symmetric |
175 | algorithms use |
176 | .I binary |
177 | keys. Keys used with number-theoretic systems (like most common |
178 | public-key systems) use |
179 | .I "multiprecision integer" |
8404fd75 |
180 | keys. Elliptic curve systems use |
181 | .I "curve point" |
182 | keys, which are either a pair of integers representing field elements, |
183 | or a `point at infinity'. Algorithms which require several key |
184 | constituents (again, like most public-key systems) use |
052b36d0 |
185 | .I structured |
8404fd75 |
186 | keys, which consist of a collection of named parts. It's possible to |
187 | store an |
188 | .I "ASCII string" |
189 | as a key, though this is usually done as a component of a structured |
190 | key. Finally, keys (including structured keys) can be encrypted. |
052b36d0 |
191 | .TP |
192 | .B "filter" |
193 | Keys and key components may be selected by a filter expression, a |
194 | sequence of flag names separated by commas. Flags are: |
195 | .BR binary , |
196 | .BR integer , |
8404fd75 |
197 | .BR struct , |
198 | .BR ec , |
199 | .BR string , |
052b36d0 |
200 | or |
201 | .B encrypt |
202 | (describing the key encoding); |
203 | .BR symmetric , |
204 | .BR private , |
8404fd75 |
205 | .BR public , |
052b36d0 |
206 | or |
207 | .B shared |
208 | (describing the category of key); |
209 | .B burn |
210 | and its negation |
211 | .B \-burn |
212 | (whether the key should be erased from memory after use); and |
213 | .B secret |
214 | and its negation |
215 | .B \-secret |
216 | (whether the key is safe to divulge). |
217 | .TP |
218 | .B "qualified tag" |
219 | A key component may be identified by the key's tag (or keyid, or type). |
220 | Subcomponents of structured keys are identified by following the tag by |
221 | a dot and the name of the subcomponent. |
d03ab969 |
222 | .TP |
223 | .B "expiry time" |
224 | Most keys expire after a certain amount of time. Once a key has |
225 | expired, it will no longer be chosen as a result of a lookup by key |
226 | type. However, it is not deleted until its deletion time is also |
227 | reached. |
228 | .TP |
229 | .B "deletion time" |
230 | A key's deletion time is the latest expiry time of any of the objects |
231 | which require that key. For example, a key used for authenticating |
232 | cryptographic cookies should have its deletion time set to the longest |
052b36d0 |
233 | expiry time of any of the cookies it can authenticate. Once a key's |
234 | deletion time is passed, it can no longer be referred to by |
d03ab969 |
235 | applications, and will be removed from the keyring next time it's |
236 | written to disk. |
237 | .TP |
052b36d0 |
238 | .B "comment" |
d03ab969 |
239 | A key may be given a comment when it's created. The comment is for the |
240 | benefit of users, and isn't interpreted by applications at all. |
241 | (Hopefully.) |
242 | .TP |
052b36d0 |
243 | .B "attributes" |
d03ab969 |
244 | A key as zero or more name/value pairs. The names and values are |
245 | arbitrary strings, except they may not contain null bytes. Some |
246 | attributes may have meaning for particular applications or key types; |
247 | others may be assigned global meanings in future. |
248 | .SH "COMMAND REFERENCE" |
249 | .SS add |
250 | The |
251 | .B add |
252 | command creates a new key and adds it to the keyring. The command |
253 | accepts the following options: |
254 | .TP |
052b36d0 |
255 | .BI "\-a, \-\-algorithm " alg |
256 | Selects a key generation algorithm. The default algorithm is |
257 | .BR binary ; |
258 | the different algorithms are described below. |
259 | .TP |
c9e31e42 |
260 | .BI "\-b, \-\-bits " bits |
d03ab969 |
261 | The length of the key to generate, in bits. The default, if this option |
052b36d0 |
262 | is not supplied, depends on the key-generation algorithm. |
263 | .TP |
264 | .BI "\-B, \-\-qbits " bits |
265 | The length of the subsidiary key or parameter, in bits. Not all |
266 | key-generation algorithms have a subsidiary key size. |
267 | .TP |
268 | .BI "\-p, \-\-parameters " tag |
269 | Selects a key containing parameter values to copy. Not all |
270 | key-generation algorithms allow the use of shared parameters. |
d03ab969 |
271 | .TP |
c9e31e42 |
272 | .BI "\-e, \-\-expire " expire |
d03ab969 |
273 | The expiry date for the generated key. This may be the string |
274 | .RB ` forever ' |
275 | if the key should never expire automatically, or any date acceptable to |
276 | the |
277 | .BR getdate (3) |
278 | library function. Briefly, |
279 | .B getdate |
280 | understands absolute dates such as |
281 | .RB ` 1999-08-02 ' |
282 | or |
283 | .RB ` "August 2nd, 1999" ', |
284 | and (perhaps more usefully) relative dates such as |
285 | .RB ` "+2 weeks" '. |
286 | The default is to allow a 2 week expiry, which isn't useful. |
287 | .TP |
c9e31e42 |
288 | .BI "\-c, \-\-comment " comment |
d03ab969 |
289 | Sets a comment for the key. The default is not to attach a comment. |
052b36d0 |
290 | .TP |
eb31b00e |
291 | .BI "\-C, \-\-curve " curve-spec |
292 | Use the elliptic curve described by |
293 | .I curve-spec |
294 | when generating elliptic curve parameters. |
295 | .TP |
052b36d0 |
296 | .BI "\-t, \-\-tag " tag |
297 | Selects a tag string for the key. The default is not to set a tag. It |
298 | is an error to select a tag which already exists. |
299 | .TP |
d07dfe80 |
300 | .BI "\-r, \-\-retag" |
301 | If a |
302 | .B \-t |
303 | option is given, remove this tag from any key which already has it. |
304 | .TP |
305 | .BI "\-R, \-\-rand-id " tag |
052b36d0 |
306 | Selects the key to use for the random number generator. Catacomb's |
307 | random number generator can be |
308 | .IR keyed , |
309 | so that, even if the inputs to the generator are compromised, knowledge |
310 | of the key is also necessary to be able to predict the output. By |
311 | default, the latest-expiring key with type |
312 | .B catacomb-rand |
313 | is used, if present; if not, no key is used. |
314 | .TP |
315 | .BI "\-l, \-\-lock" |
316 | Requests that the secret parts of the newly-generated key be encrypted |
317 | using a passphrase. |
318 | .TP |
319 | .BI "\-q, \-\-quiet" |
320 | Suppresses the progress indication which is usually generated while |
321 | time-consuming key generation tasks are being performed. |
1476eebc |
322 | .TP |
323 | .BI "\-L, --lim-lee" |
324 | When generating Diffie-Hellman parameters, generate a Lim-Lee prime |
325 | rather than a random (or safe) prime. See the details on Diffie-Hellman |
326 | key generation below. |
327 | .TP |
328 | .BI "\-S, --subgroup" |
329 | When generating Diffie-Hellman parameters with a Lim-Lee prime, choose a |
330 | generator of a prime-order subgroup rather than a subgroup of order |
331 | .RI ( p "- 1)/2." |
d03ab969 |
332 | .PP |
333 | The key's type is given by the required |
334 | .I type |
335 | argument. Following the type are zero or more attributes, which are |
336 | attached to the key in the same way as for the |
337 | .B setattr |
338 | command. |
339 | .PP |
052b36d0 |
340 | The key-generation algorithms supported are as follows: |
341 | .TP |
342 | .B "binary" |
343 | Generates a plain binary key of the requested length. If the requested |
344 | key length is not a multiple of eight, the high-order bits of the first |
345 | octet of the key are zeroed. The default key length is 128 bits. |
346 | .TP |
347 | .B "des" |
348 | Generates a DES key, with parity bits. The key length must be 56, 112 |
349 | or 168; the default is 56. The low-order bit of each octet is ignored by |
350 | the DES algorithm; it is used to give each octet odd parity. |
351 | .TP |
352 | .B "rsa" |
353 | Generates a public/private key pair for use with the RSA algorithm. |
354 | .IP |
355 | The key components are |
356 | .I p |
357 | and |
358 | .IR q , |
359 | a pair of prime numbers; |
360 | .IR n , |
361 | the product of |
362 | .I p |
363 | and |
364 | .IR q ; |
365 | .IR e , |
366 | the public exponent; |
367 | .IR d , |
368 | the private exponent, chosen such that |
369 | .IR ed \ \(==\ 1 |
370 | (mod |
371 | .RI ( p \ \-\ 1)( q \ \-\ 1)); |
372 | and some other values useful for optimizing private-key operations: |
373 | .IR q \*(ss\-1\*(se\ mod\ p , |
374 | .IR d \ mod\ p \ \-\ 1, |
375 | and |
376 | .IR d \ mod\ q \ \-\ 1. |
377 | The values |
378 | .I n |
379 | and |
380 | .I e |
381 | constitute the public key; the rest must be kept secret. The key size |
382 | requested by the |
383 | .B \-b |
384 | option determines the size of the modulus |
385 | .IR n ; |
386 | the default is 1024 bits. |
387 | .IP |
388 | The key generation algorithm chooses |
389 | .I p |
390 | and |
391 | .I q |
392 | to be |
393 | .I strong |
394 | primes: both |
395 | .IR p \ \-\ 1 |
396 | and |
397 | .IR p \ +\ 1 |
398 | have large prime factors \- call them |
399 | .I r |
400 | and |
401 | .I s |
402 | respectively \- and |
403 | .IR r \ \-\ 1 |
404 | also has a large prime factor; |
405 | .I q |
406 | has similar properties. |
407 | .IP |
408 | The modulus |
409 | .I n |
410 | cannot be sensibly used as a shared parameter, since knowledge of |
411 | corrssponding public and private exponents is sufficient to be able to |
412 | factor the modulus and recover other users' private keys. |
413 | .TP |
eb31b00e |
414 | .B "dh-param" |
052b36d0 |
415 | Generates parameters for use with the Diffie-Hellman key exchange |
416 | protocol, and many related systems, such as ElGamal encryption and |
1476eebc |
417 | signatures, and even DSA. (The separate DSA algorithm uses the |
418 | generator described in FIPS186-1.) |
419 | .IP |
420 | The Diffie-Hellman parameters are a prime modulus |
421 | .I p |
052b36d0 |
422 | and a generator |
423 | .I g |
1476eebc |
424 | of a subgroup of |
425 | .BR Z / \c |
426 | .IB p Z |
427 | of order |
428 | .IR q . |
429 | The |
052b36d0 |
430 | .B \-b |
1476eebc |
431 | option controls the size of the modulus |
052b36d0 |
432 | .IR p ; |
1476eebc |
433 | the default size is 1024 bits. |
434 | .IP |
435 | If no |
052b36d0 |
436 | .I q |
1476eebc |
437 | size is selected using the |
052b36d0 |
438 | .B \-B |
1476eebc |
439 | option and the Lim-Lee prime option is disabled, then |
440 | .I p |
441 | is chosen to be a `safe' prime (i.e., |
052b36d0 |
442 | .IR p \ =\ 2 q \ +\ 1, |
1476eebc |
443 | with |
444 | .I q |
8404fd75 |
445 | prime). Finding safe primes takes a very long time. In this case, the |
446 | value of |
1476eebc |
447 | .I g |
448 | is fixed as 4. |
449 | .IP |
450 | If a size is chosen for |
451 | .I q |
452 | and Lim-Lee primes are not selected then the prime |
453 | .I q |
454 | is generated and |
455 | .I p |
456 | is chosen so that |
457 | .IR p \ \-\ 1 |
458 | is a multiple of |
459 | .IR q . |
460 | .IP |
461 | If the |
462 | .B \-L |
463 | option was given Lim-Lee primes are selected: the parameters are chosen |
464 | such that |
465 | .IR p \ =\ 2\ q \*(us0\*(ue\ q \*(us1\*(ue\ q \*(us2\*(ue\ ...\ +\ 1, |
466 | where the |
467 | .IR q \*(us i\*(ue |
468 | are primes at least as large as the setting given by the |
469 | .B \-B |
470 | option (or 256 bits, if no setting was given). |
052b36d0 |
471 | .IP |
1476eebc |
472 | If the |
473 | .B \-S |
474 | option was given, the generator |
475 | .I g |
476 | is chosen to generate the subgroup of order |
477 | .IR q \*(us0\*(ue; |
478 | otherwise, |
479 | .I g |
480 | will generate the group of order |
481 | .RI ( p \ \-\ 1)/2\ =\ q \*(us0\*(ue\ q \*(us1\*(ue\ q \*(us2\*(ue\ ... |
8404fd75 |
482 | .IP |
483 | Finally, the |
484 | .B \-C |
485 | option can be given, in which case the parameters are taken directly |
486 | from the provided group specification, which may either be the the name |
487 | of one of the built-in groups (say |
488 | .B "key add \-a dh\-param \-C list 42" |
489 | for a list) or a triple |
490 | .RI ( p ,\ q ,\ g ). |
491 | separated by commas. No random generation is done in this case: the |
492 | given parameters are simply stored. |
052b36d0 |
493 | .TP |
494 | .B "dh" |
495 | Generates a public/private key pair for use with offline Diffie-Hellman, |
496 | ElGamal, DSA or similar discrete-logarithm-based systems. It selects a |
497 | private key |
498 | .IR x \ <\ q , |
499 | and computes the public key |
500 | .IR y \ =\ g\*(ssx\*(se \ mod\ p . |
501 | .TP |
502 | .B "dsa-param" |
503 | Generates parameters for the DSA algorithm. DSA parameters are also |
504 | suitable for use with Diffie-Hellman and ElGamal system. |
505 | .IP |
506 | The main difference between DSA and Diffie-Hellman parameter generation |
507 | is thatthe DSA parameter generation |
508 | algorithm creates a |
509 | .I seed |
510 | from which the parameters are derived, and, assuming that the SHA-1 hash |
511 | function is strong, it's not feasible to construct a seed from which |
512 | deliberately weak parameters are derived. The algorithm used is the one |
513 | described in the DSA standard, FIPS\ 186, extended only to allow |
514 | sequential search for a prime |
515 | .I q |
516 | and to allow arbitrary parameter sizes. The seed is stored, |
517 | Base64-encoded, as the value of the attribute |
518 | .BR seed . |
519 | .IP |
520 | The default lengths for |
521 | .I p |
522 | and |
523 | .I q |
524 | are 768 and 160 bits respectively, since the DSA standard specifies that |
525 | .I q |
526 | be 160 bits, and the choice of 768 bits for |
527 | .I p |
528 | gives commensurate security. |
529 | .TP |
530 | .B "dsa" |
531 | Generates a public/private key pair for DSA. As for Diffie-Hellman |
532 | keys, it selects a |
533 | private key |
534 | .IR x \ <\ q , |
535 | and computes the public key |
536 | .IR y \ =\ g\*(ssx\*(se \ mod\ p . |
537 | .TP |
538 | .B "bbs" |
539 | Generates a public/private key pair for the Blum-Blum-Shub random-number |
540 | generator, and the Blum-Goldwasser semantically-secure public-key |
541 | encryption system. |
542 | .IP |
543 | The key components are prime numbers |
544 | .I p |
545 | and |
546 | .IR q , |
547 | both congruent to 3 (mod\ 4), and their product |
548 | .IR n . |
549 | The public key is simply the modulus |
550 | .IR n ; |
551 | the factors |
552 | .I p |
553 | and |
554 | .I q |
555 | are the private key. |
556 | .IP |
557 | The key-generation algorithm ensures that the two primes |
558 | .I p |
559 | and |
560 | .I q |
561 | are |
562 | .I strong |
563 | (see the discussion of strong primes above, in the section on RSA keys), |
564 | and that |
565 | .RI ( p \ \-\ 1)/2 |
566 | and |
567 | .RI ( q \ \-\ 1)/2 |
568 | are relatively prime, giving a maximum possible period length. |
569 | .IP |
570 | The key size requested by the |
571 | .B \-b |
572 | option determines the length of the modulus |
573 | .IR n ; |
574 | the default length is 1024 bits. |
eb31b00e |
575 | .TP |
576 | .B "ec-param" |
577 | Store an elliptic curve specification. If no explicit |
578 | .I curve-spec |
579 | is given (the |
580 | .RB ` \-C ' |
581 | option) then a curve is chosen whose order is about the size given by the |
582 | .RB ` \-b ' |
583 | option (default is 256 bits). |
584 | .IP |
585 | A |
586 | .I curve-spec |
587 | can be given explicitly (in which case |
588 | .RB ` \-b ' |
589 | is ignored). It can either be the name of a built-in curve (say |
8404fd75 |
590 | .B "key add \-a ec\-param \-C list 42" |
eb31b00e |
591 | for a list of curve names) or a full specification. The curve is |
592 | checked for correctness and security according to the SEC1 |
593 | specification: failed checks cause a warning to be issued to standard |
594 | error (though the program continues anyway). The check can be |
595 | suppressed using the |
596 | .RB ` \-q ' |
597 | option. |
598 | .IP |
599 | A curve specification consists of the following elements optionally |
600 | separated by whitespace: a |
601 | .IR "field type" , |
602 | which is one of |
603 | .BR "prime" , |
604 | .BR "niceprime" , |
8404fd75 |
605 | .BR "binpoly" , |
606 | .or |
607 | .BR "binnorm" ; |
eb31b00e |
608 | an optional |
609 | .RB ` : '; |
610 | the field modulus |
611 | .IR p ; |
8404fd75 |
612 | if the field type is |
613 | .B binnorm |
614 | then an optional |
615 | .RB ` , ' |
616 | and the representation of the normal element \*(*b; an optional |
eb31b00e |
617 | .RB ` / '; |
618 | a |
619 | .IR "curve type" , |
620 | which is one of |
621 | .BR "prime" , |
622 | .BR "primeproj" , |
623 | .BR "bin" , |
624 | and |
625 | .BR "binproj" |
626 | (the `proj' types currently have much better performance); |
627 | an optional |
628 | .RB ` : '; |
629 | the two field-element parameters |
630 | .I a |
631 | and |
632 | .IR b |
633 | which define the elliptic curve |
634 | .IR E , |
635 | separated by an optional |
636 | .RB ` , '; |
637 | an optional |
638 | .RB ` / '; |
639 | the |
640 | .IR x - |
641 | and |
642 | .IR y -coordinates |
643 | of the generator point |
644 | .IR G , |
645 | separated by an optional |
646 | .RB ` , '; |
647 | an optional |
648 | .RB ` : '; |
649 | the order |
650 | .I r |
651 | of the group generated by |
652 | .IR G ; |
653 | an optional |
654 | .RB ` * '; |
655 | and the |
656 | .I cofactor |
657 | .I h |
658 | = |
659 | .RI # E / r . |
660 | .TP |
661 | .B "ec" |
662 | Generate a private scalar and a corresponding public point on an |
663 | elliptic curve. See |
664 | .B ec-param |
665 | above for how to specify elliptic curve parameter sets. The scalar |
666 | .I x |
667 | is chosen unformly between 0 and the curve order |
668 | .IR r ; |
669 | the public point is then |
670 | .I x |
671 | \(mu |
672 | .IR G . |
052b36d0 |
673 | .SS "expire" |
d03ab969 |
674 | Forces keys to immediately expire. An expired key is not chosen when a |
675 | program requests a key by its type. The keys to expire are listed by |
676 | their |
052b36d0 |
677 | .IR tag s. |
678 | .SS "delete" |
d03ab969 |
679 | Deletes keys immediately. The keys to delete are listed by their |
052b36d0 |
680 | .IR tag s. |
d03ab969 |
681 | Be careful when deleting keys. It might be a better idea |
682 | to expire keys rather than deleting them. |
052b36d0 |
683 | .SS "tag" |
684 | Sets, deletes or changes the tag attached to a key. The first tag or |
685 | keyid names the key to be modified; the second, if present specifies the |
686 | new tag to be set. If no second argument is given, the existing tag, if |
d07dfe80 |
687 | any, is removed and no new tag is set. It is an error to set a tag |
688 | which already exists on another key, unless you give the |
689 | .B \-r |
690 | option, which removes the tag first. |
052b36d0 |
691 | .SS "setattr" |
d03ab969 |
692 | Attaches attributes to a key. The key to which the attributes should be |
693 | attached is given by its |
052b36d0 |
694 | .IR tag . |
d03ab969 |
695 | Each attribute has the form |
696 | .IB name = value\fR. |
697 | An attribute can be deleted by assigning it an empty value. Although |
698 | the keyring file format is capable of representing an attribute with an |
699 | empty value as distinct from a nonexistant attribute, this interface |
700 | does not allow empty attributes to be set. |
052b36d0 |
701 | .SS "comment" |
702 | Sets, deletes or changes the comment attached to a key. The first |
703 | argument is a key tag or keyid which names the key to be modified; the |
704 | second, if present, is the new comment. If no second argument is given, |
705 | the existing comment, if any, is removed, and no new comment is set. |
706 | .SS "lock" |
707 | Locks a key or key component using a passphrase. If the key is already |
708 | locked, the existing passphrase is requested, and a new passphrase is |
709 | set. |
710 | .SS "unlock" |
711 | Unlocks a passphrase-locked key or key component. If the key is not |
712 | locked, an error is reported. |
713 | .SS "list" |
d03ab969 |
714 | Lists the keys in the keyring. A couple of options are supported: |
715 | .TP |
716 | .B "\-v, \-\-verbose" |
717 | Increases the amount of information displayed for each key. Repeat for |
718 | a greater effect. |
719 | .TP |
720 | .B "\-q, \-\-quiet" |
721 | Decreases the amount of information displayed for each key. Each use |
722 | cancels a |
723 | .RB ` \-v ' |
724 | option. |
c9e31e42 |
725 | .TP |
726 | .B "\-u, \-\-utc" |
727 | Display key expiry times as UTC rather than using the local time zone. |
052b36d0 |
728 | .TP |
729 | .BI "\-f, \-\-filter " filter |
730 | Specifies a filter. Only keys and key components which match the filter |
731 | are listed. |
d03ab969 |
732 | .PP |
733 | By default, a single line of output is generated for each, showing |
734 | keyids, types, expiry and deletion dates, and comments. Additional |
735 | .RB ` \-v ' |
736 | options show more information, such as the exact time of day for expiry |
052b36d0 |
737 | and deletion, key attributes, and a dump of the actual key data. If the |
738 | verbosity level is sufficiently high, passphrases are requested to |
739 | decrypt locked keys. Make sure nobody is looking over your shoulder |
740 | when you do this! |
741 | .SS "fingerprint" |
742 | Reports a fingerprint (secure hash) on components of requested keys. |
743 | The following option is supported: |
744 | .TP |
745 | .BI "\-f, \-\-filter " filter |
746 | Specifies a filter. Only keys and key components which match the filter |
747 | are fingerprinted. The default is to only fingerprint nonsecret |
748 | components. |
b817bfc6 |
749 | .TP |
750 | .BI "\-a, \-\-algorithm " hash |
751 | Names the hashing algorithm. Run |
752 | .B hashsum -a list |
753 | for a list of hashing algorithms. The default is |
754 | .BR rmd160 . |
052b36d0 |
755 | .PP |
756 | The keys to be fingerprinted are named by their tags or keyids given as |
757 | command line arguments. If no key tags are given, all keys which match |
b817bfc6 |
758 | the filter are fingerprinted. See |
759 | .BR keyring (5) |
760 | for a description of how key fingerprints are computed. |
052b36d0 |
761 | .SS "tidy" |
d03ab969 |
762 | Simply reads the keyring from file and writes it back again. This has |
763 | the effect of removing any deleted keys from the file. |
052b36d0 |
764 | .SS "extract" |
765 | Writes a selection of keys to a file. An option is supported: |
766 | .TP |
767 | .BI "\-f, \-\-filter " filter |
768 | Specifies a filter. Only keys and key components which match the filter |
769 | are written. |
770 | .PP |
771 | Keys extracted are written to the file named by the first argument, |
d03ab969 |
772 | which may be |
773 | .RB ` \- ' |
774 | to designate standard output. The keys to extract are listed by their |
052b36d0 |
775 | tags; if no tags are given, all keys which match the filter are |
776 | extracted. The output is a valid keyring file. |
777 | .SS "merge" |
d03ab969 |
778 | Merges the keys from the named |
779 | .IR file , |
780 | which may be |
781 | .RB ` \- ' |
782 | to designate standard input, with the keyring. Keys already in the |
783 | keyring are not overwritten: you must explicitly remove them first if |
784 | you want them to be replaced during the merge. |
d03ab969 |
785 | .SH "SEE ALSO" |
786 | .BR keyring (5). |
787 | .SH AUTHOR |
788 | Mark Wooding, <mdw@nsict.org> |
789 | |