lbdb & m_gpg
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
Re: lbdb & m_gpg
Hi again! ...and then David @ BigFoot said... % Hi, folks -- % % More of the same here. It seems that m_gpg doesn't give me back all of In fact, it seems on second look that m_gpg *does* give me all of my entries. Further digging reveals that both key addresses end up in $collection after lbdbq calls m_gpg_query and that they get stripped by munge and munge-keeporder. I'm not exactly sure what's going on in munge-keeporder, but munge appears to be building an array (named "line") indexed by email address -- only. Have I stumbled on a limitation of lbdbq and munge, or has my habit of keeping keys to decrypt old messages messed me up unlike anyone else? TIA^^2 :-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
Re: lbdb & m_gpg
I have no problems, i don't see how this all is happening. It was pretty p`n`p for me.. I suggest using the global file. For some reason there were issues with the installation taking my home directory settings. On Fri, Aug 25, 2000 at 01:33:39PM -0400, David T-G muttered: | Hi again! | | ...and then David @ BigFoot said... | % Hi, folks -- | % | % More of the same here. It seems that m_gpg doesn't give me back all of | | In fact, it seems on second look that m_gpg *does* give me all of my | entries. Further digging reveals that both key addresses end up in | $collection after lbdbq calls m_gpg_query and that they get stripped by | munge and munge-keeporder. I'm not exactly sure what's going on in | munge-keeporder, but munge appears to be building an array (named "line") | indexed by email address -- only. | | Have I stumbled on a limitation of lbdbq and munge, or has my habit of | keeping keys to decrypt old messages messed me up unlike anyone else? | | | TIA^^2 | | :-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* | -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: lbdb & m_gpg
Jason -- ...and then Jason Helfman said... % I have no problems, i don't see how this all is happening. It was pretty % p`n`p for me.. Well, that's good. Do you have multiple keys with the same address in your GPG keyring? If not, can I send you a couple so that you can see what you get? % % I suggest using the global file. For some reason there were issues with % the installation taking my home directory settings. That's good to know. The plan is to eventually put it into /usr/local, but I wanted to do my testing and repeated building somewhere else (like where I have permission!). I'm surprised that it should make a difference, especially in this case where I've traced it down to an apparent design limitation (still no idea on the m_muttalias problem, but I also dunno if I have my aliases in the expected format). Thanks! :-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
Re: lbdb & m_gpg
I have multiple keys for Roland. It comes up fine. On Fri, Aug 25, 2000 at 02:07:45PM -0400, David T-G muttered: | Jason -- | | ...and then Jason Helfman said... | % I have no problems, i don't see how this all is happening. It was pretty | % p`n`p for me.. | | Well, that's good. Do you have multiple keys with the same address in | your GPG keyring? If not, can I send you a couple so that you can see | what you get? | | | % | % I suggest using the global file. For some reason there were issues with | % the installation taking my home directory settings. | | That's good to know. The plan is to eventually put it into /usr/local, | but I wanted to do my testing and repeated building somewhere else | (like where I have permission!). I'm surprised that it should make | a difference, especially in this case where I've traced it down to an | apparent design limitation (still no idea on the m_muttalias problem, | but I also dunno if I have my aliases in the expected format). | | Thanks! | | | :-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* | -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
Re: lbdb & m_gpg
On Fri, 25 Aug 2000, David T-G wrote: > pub 1024D/AFEFC23B 2000-06-29 jimh <[EMAIL PROTECTED]> > pub 1024D/401A068F 1998-09-03 PHXMGNT <[EMAIL PROTECTED]> > I did my same trick of commenting out the greps and seds, and this > time the "problem" showed up at only the second line. > In fact, it seems on second look that m_gpg *does* give me all of my > entries. Further digging reveals that both key addresses end up in > $collection after lbdbq calls m_gpg_query and that they get stripped > by munge and munge-keeporder. That's the point. > I'm not exactly sure what's going on in munge-keeporder, but munge > appears to be building an array (named "line") indexed by email > address -- only. Yes. This is a feature :-) My understanding of a mail address is that it is unique to a user (with a user name). So deduping means to reduce multiple lines with the same mail address but different user names to one line. Otherwise you usually have multiple lines like this: foo@bar User Name foo@bar "User Name" foo@bar User M. Name foo@bar "User M. Name" foo@bar user name foo@bar User M . Name foo@bar "User M . Name" Or something like this, which doesn't make much sense. For this the munge algorithm reduces all lines for one mail address to one line (with a randomly chosen real name). > Have I stumbled on a limitation of lbdbq and munge, or has my habit > of keeping keys to decrypt old messages messed me up unlike anyone > else? Don't forget that lbdb isn't used for decrypting mail but only for collecting mail addresses and attached user names. It is intended to find hopefully all matching addresses/user names and to offer not too many duplicates, which would make it useless. But I added a line to the TODO list to think about changing this behavior... Tscho Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ *
Re: lbdb & m_gpg
On Fri, Aug 25, 2000 at 01:21:00PM -0400, David T-G wrote: > 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. The m_pgp module of lbdb doesn't return keys, it returns email addresses. Why does it matter which key was used to select the address, both keys have the same address? > Any idea what's up this time? I don't think I could be storing my keys in > the wrong format ;-) The only "problem" here is that you're focusing on keys when you really should be concerning yourself with email addresses. -- Take a look in Hagbard's World: | mutt.octet.filter - autoview octet-streams http://www.hagbard.demon.co.uk/ | mutt.vcard.filter - autoview simple vcards http://www.acemake.com/hagbard/ | muttrc2html - muttrc -> HTML utility Free software, including| muttrc.sl - Jed muttrc mode
Re: lbdb & m_gpg
Roland and Dave -- ...and then Roland Rosenfeld said... % On Fri, 25 Aug 2000, David T-G wrote: % % > $collection after lbdbq calls m_gpg_query and that they get stripped % > by munge and munge-keeporder. % % That's the point. Gotcha. % % > I'm not exactly sure what's going on in munge-keeporder, but munge % > appears to be building an array (named "line") indexed by email % > address -- only. % % Yes. This is a feature :-) Hokay :-) % % > Have I stumbled on a limitation of lbdbq and munge, or has my habit % > of keeping keys to decrypt old messages messed me up unlike anyone % > else? % % Don't forget that lbdb isn't used for decrypting mail but only for % collecting mail addresses and attached user names. It is intended to Hmmm... Well, that is a good point. I was thinking of it perhaps as a little DB of more things, like not just email addresses but also what keys are available and so on (more that I had not yet dreamed up ;-) % find hopefully all matching addresses/user names and to offer not too % many duplicates, which would make it useless. Gotcha. % % But I added a line to the TODO list to think about changing this % behavior... In retrospect I now understand this, so perhaps it needs not a change in behavior but a change in level of expectation or perception (or maybe just a change of user! :-) % % Tscho % % Roland % % -- % * [EMAIL PROTECTED] * http://www.spinnaker.de/ * ...and then Dave Pearson said... % On Fri, Aug 25, 2000 at 01:21:00PM -0400, David T-G wrote: % % > Any idea what's up this time? I don't think I could be storing my keys in % > the wrong format ;-) % % The only "problem" here is that you're focusing on keys when you really % should be concerning yourself with email addresses. That makes sense, especially in retrospect. While not worrying about using lbdb for decrypting, I was thinking of how it would be used to select keys, and the answers is that it probably won't... % % -- % Take a look in Hagbard's World: | mutt.octet.filter - autoview octet-streams % http://www.hagbard.demon.co.uk/ | mutt.vcard.filter - autoview simple vcards % http://www.acemake.com/hagbard/ | muttrc2html - muttrc -> HTML utility % Free software, including| muttrc.sl - Jed muttrc mode :-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
