Detection of sign-only vs. sign-and-encrypt keys
mail at mark-kirchner.de
Tue Jun 29 21:31:43 CEST 2004
On Tuesday, June 29, 2004, 3:21:47 AM, Carl wrote:
>> Look in the 11th field. Capital S means the key can sign. Capital E
>> means the key can encrypt. Capital C means the key can certify
>> (i.e. sign other keys).
> pub:-:1024:17:A347DE566D347FFF:2000-05-22:::-:Dan Stromberg
> <strombrg at uci.edu>::scESC:
> pub:-:1024:17:F04287FDA2667802:2003-10-19:::-:Peter Kerekes
> <pkerekes at ca.inter.net>::scESC:
> pub:-:1024:17:2014F5DBAE127015:2001-04-14:2008-02-24::-:Todd A. Lyons
> (Cannonball) <todd at mrball.net>::scESC:
> Interesting I get only lowercase letters not the capitols you indicate.
I don't think so, see above. Well, it's the twelfth field, if you
start counting with the "pub" / "sub" field. And you have to start
your counting with "1"...
On second thought, one could argue that it's a kind of an array, so
starting with "0" would be justified... :-)
The subkeys you listed have only lowercase letters, right. According
to the docs/DETAILS.TXT file, the uppercase letters are given for the
primary key only: "To denote the _usable_ capabilities of the entire
> Note some have more than one letter.
Yes, since a lot of keys can encrypt, sign and certify (or any
combination of that).
Stolen sigline of the day:
You may have to right to bear arms but I have the right to arm bears.
SCNR, really... :-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 183 bytes
Desc: not available
Url : /pipermail/attachments/20040629/99d01923/attachment.bin
More information about the Gnupg-users