Mailing List Archive

cipher.c and pubkey.c [Re: rsa/idea/skipjack...]
El mar, 23 de nov de 1999, a las 01:28:45 +0100, Thomas Weinbrenner dijo:
>
> Then put the modules in /usr/local/gnupg/

Well, the modules are in /usr/local/lib/gnupg/, and this seems to be
right.

> and add to your ~/.gnupg/options
>
> load-extension idea
> load-extension rsa
> load-extension skipjack

My most sincere apologies, I had these lines commented, thank you!

Now, according to the documentation, the file gnupg/cipher/cipher.c can
be easily hacked to include idea support, and so can be
gnupg/cipher/pubkey.c to include rsa support (though it claims to be not
as easy to hack as cipher.c). What would be the difference in modifying
these files and adding idea and/or rsa support to them? (compared to the way
I used to add idea and rsa support, ie. by just compiling the modules and
modifying ../cipher/Makefile.in)


Thank You,

--
Horacio Anno MMDCCLII ad Urbe condita
mailto:homega@ciberia.es
~ Spain ~Spanje ~ Spanien
--------------------------------------------------------------------
Key fingerprint = F4EE AE5E 2F01 0DB3 62F2 A9F4 AD31 7093 4233 7AE6
Re: cipher.c and pubkey.c [ In reply to ]
J Horacio MG <homega@ciberia.es> writes:

> Now, according to the documentation, the file gnupg/cipher/cipher.c can
> be easily hacked to include idea support, and so can be
> gnupg/cipher/pubkey.c to include rsa support (though it claims to be not

No. The configure script builds a cipher/constructor.c file and links
the modules this way.

And please don't use skipjack.c anymore - to make this clear I have removed
it from the FTP server.




--
Werner Koch at guug.de www.gnupg.org keyid 621CC013