On Mon, Nov 22, 1999 at 11:04:26PM +0000, Sean Rima wrote:
> Hi A!
>
> On Mon, 22 Nov 1999, A Guy Called Tyketto wrote:
>
> > > > Why not have one gpg (or pgp) config file for all correspondents?
> > > >
> > > The problem is the fact that there are a few people on the Mutt list who use
> > > PGP2 and PGP5. These keys are not able to be used in GPG AFAIK. I have both
> > > GPG and PGP to get around this but would like to be able to set Mutt to
> > > choice the correct encryption tool depending on who the message is from
> > >
> > > Sean
> >
> > There's two ways to do this.
> >
> > First, to solve the receiving part, on your end. grab the rsa.c
> > program that's on the GnuPG FTP site (ftp.gnupg.org:/pub/gcrypt/contrib). That
> > will allow you to use GnuPG, to decrypt keys signed by PGP2 (which uses RSA).
> > With that, there is also an option that you can pass to GnuPG, that could sign
> > with an RSA key, that PGP2 would be able to understand. PGP5 should have no
> > problem with GnuPG, for sending or receiving. But, that extension for RSA
> > saved me a lot of trouble with GnuPG. Try it.
> >
>
> I grabbed rsa.c and idea.c and compiled and put to the lib directory. I then
> tried a couple of archived messages available but still it says the
> encryption is unknown. One did say about Not being a self signed sig.
Extend your ~/.gnupg/options file to contain:
load-extension /usr/lib/gnupg/rsa
load-extension /usr/lib/gnupg/idea
MfG, JBG
--
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
PGP signature
