Decryption problem
Johan Wevers
johanw@vulcan.xs4all.nl
Tue, 14 Sep 1999 23:16:18 +0200 (MET DST)
Werner Koch wrote:
> Well, you know that this is patented - hope you are only doing this
> for research.
No, for real (non-commercial) use. And I don't care that is is patented.
I use IDEA (and RSA, but I'm outside the US) with 2.x anyway.
> > load-extension skipjack
>
> DONT USE THIS CIPHER - I simply wrote it to see how fast I can
> implement a new cipher.,
I'm not using it for encryption, but I reasoned that it wouldn't hurt to be
able to decrypt messages encrypted with Skipjack.
> GUESS WHY THE NSA RELEASED THESE SECRET ALGORITHM TO THE PUBLIC?
> IT HAS SEVERAL WEAKNESSES
They also released SHA-1...
> and is not OpenPGP compliant.
In what way? That is not one of the prescribed algorithms?
BTW, I'm trying to make an RC5 module myself to see if I really understand
the code. I'm only confused what to do with the fact that my RC5 example
code gets pointers to 32 bits quantities and the gpg code needs byte*'s, but
I guess this subject is more approprriate for the developer list.
> > vulcan:~/tmp> gpg --rfc1991 --s2k-digest-algo MD5 --digest-algo MD5
> > --cipher-algo IDEA --s2k-cipher-algo IDEA -u johanw filename
>
> Add a "-e" to encrypt and "-r" for the recipient of the message
Thanks. Now pgp 2.6.3i is able to decrypt the message. With the options file
settings I have the -r and -e options where the only ones required.
2.x compatibility is required since some of my correspondents use 2.x
versions and I don't want to force them to upgrade. However I consider
changing to a pgp 5 compatible key because the MD5 algorithm is not really
considered safe anymore. Being compatible when just using conventional
encryption would be nice, but I'll keep a pgp 2 binary around.
--
ir. J.C.A. Wevers // Physics and science fiction site:
johanw@vulcan.xs4all.nl // http://www.xs4all.nl/~johanw/index.html
Finger johanw@xs4all.nl for my PGP public key. PGP-KeyID: 0xD42F80B1