Mailing List Archive

loading idea and rsa extensions
I wish to use the idea and rsa extensions. I compiled idea.c and rsa.c
from the gnupg.org ftp site as from the compilation instructions in
the source, copied idea and rsa in /usr/local/lib/gnupg (default,
never changed), added load-extension rsa and load-extension idea in
.gnupg, and it does not work. gpg --version does not see the new
modules. I read all the related posts I found on the mailing list
archives, as far as I can tell I did everything right, but does not
work. Any help?
Re: loading idea and rsa extensions [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

At 09:20 04.03.00 +0100, Jonas Steverud wrote:
>Gamma Pi <gammapi@newsguy.com> writes:

>> added load-extension rsa and load-extension idea in
>> .gnupg, and it does not work.

>I have
>load-extension ~/bin/GnuPG/lib/idea
>load-extension ~/bin/GnuPG/lib/rsa
>in my ~/.gnupg/options. Maybe load-extension needs the entire path?

>(Documentation bug?)

definetly not. 'load-extension idea' works fine for me.
The problem must lay elsewhere. It's intresting that Gamma Pi does
not seem to get any error messages. If you changed the right option
file, and gpg can't find an extension you specified, you should get a
message like:
'/usr/local/lib/gnupg/rsa : cannot open shared object file: ...blah,
blah ,blah'
So maybe gpg is not reading the 'options' file you think, or there is
something wrong with the load extension line. However this should
give you a message like this:
'gpg: /home/jerome/.gnupg/options:73: invalid option'
unless it begins with '#', which would be a pretty trivial error :-)
However shit happens :-)

If this won't help you, I am pretty clueless.

CU,
Jerome

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.1 Int.

iQA/AwUBOMDaQnobwxDFphpGEQKRugCg8D3sT9ljutAcl2jClAPKLRiSmlsAn31p
wDJBOeZfOWprrDBCxs6VG3T6
=c86I
-----END PGP SIGNATURE-----
Re: loading idea and rsa extensions [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for all comments ... it was simpler than that. I had built gpg
without support for dynamic linking. I rebuilt it and it works fine!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>

iD8DBQE4wlD5IN3JgRjwykYRAj4bAJ0V/hddxAJEcVxDk2J8D3rggiqF3ACguUL3
IyZPgmbdMMgDP6+XTneZT9w=
=dabL
-----END PGP SIGNATURE-----