Hi, folks --
More of the same here. It seems that m_gpg doesn't give me back all of
the entries, which means so far that I don't get the ones I want!
I have a number of keys (7 or 8), and lbdbq only returns three. A simpler
case might be to try that of my pal Jim, whose old and new keys I have.
Running
gpg --list-keys jimh
gives me
pub 1024D/AFEFC23B 2000-06-29 jimh <[EMAIL PROTECTED]>
sub 4096g/ED49589E 2000-06-29
pub 1024D/401A068F 1998-09-03 PHXMGNT <[EMAIL PROTECTED]>
sub 2048g/12BE4CB3 1998-09-03
(to set the stage). Running lbdbq using only m_gpg, however, only
returns the PHXMGNT key, which is a real bummer since it's the old one.
I did my same trick of commenting out the greps and seds, and this
time the "problem" showed up at only the second line. The m_gpg script
looks like
...
$GPG --list-keys --with-colons "$@" 2>/dev/null \
| grep '^\(pub\|uid\):\([^:]*:\)\{8,8\}[^<>:]* <[^<>@: ]*@[^<>@: ]*>[^<>@:]*:'
\
| sed -e 's/^\([^:]*:\)\{9,9\}\([^<:]*\) <\([^>:]*\)>.*:.*$/\3 \2
(GnuPG)/' \
| sed -e 's/ \([^ ]\{27,27\}\)[^ ]* / \1... /'
...
and I have to dump the second line (the first sed line) in order to have
both keys show up (in their colon format); as soon as I put that one
back in, I get only one key, as
[EMAIL PROTECTED] PHXMGNT (GnuPG)
Any idea what's up this time? I don't think I could be storing my keys
in the wrong format ;-)
TIA & HAND
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
