Hi, all -- I've just finished sweating out the details of how gpg 1.0.7 handles keyrings and imported keys (*vastly* differently from 1.0.6 and predecessors, adding to my feeling that this should have been gpg 1.1.0 instead of such a minor revision) and basically the only way to get an imported key to land in a particular ring is to list that ring first in the options file (since I believe, though I'm not positive 'cuz I haven't tested *that* thoroughly, that even a ring specified on the command line will be "last" in the list). I can see two ways to do that: generate [at least part of] the options file dynamically, a la through a source command, or with a gpg wrapper. I'm childishly hopeful of the former but not so much that I don't think that the latter is the way I'll end up going.
What I need to know now is how mutt calls gpg so that it gets a key; I don't think that pgp_getkeys_command is ever actually run. If I turn off automatic key retreival in my options file I imagine gpg will come back and say "I don't have the key", just like when it can't find it from a keyserver. What then, though, causes a download? If it's sufficient to simply wrap gpg all of the time then that makes things simple in one way, whereas if I wrap gpg only in pgp_getkeys_command it makes it simple in another. I hope this question doesn't belong on mutt-dev, since I'm not subscribed over there :-) We'll see, I suppose. 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.justpickone.org/davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
msg28114/pgp00000.pgp
Description: PGP signature
