Hallo,
Thomas Bushnell BSG schrieb:
Well, IIRC libaqbanking itself doesn't use libssl, its dependency
libgwenhywfar does. Now, crypto may be pluggable in gwenhywfar also, but
what does that gain us?
Actually, aqbanking *does* use SSL:
I tried to track this down in the build process. Therefor I configured
aqbanking without aqhbci and aqofx backend and cbanking frontend only.
I don't know yet why at all, but the only times ssl or crypt is
mentioned in the build process is when building the bankinfo plugin:
Making all in de
make[5]: Entering directory
`/home/micha/dev/aqbanking/aqbanking-svn/src/plugins/bankinfo/de'
[...]
gcc -shared .libs/de.o -Wl,--whole-archive
../generic/.libs/libbankinfo.a -Wl,--no-whole-archive -Wl,--rpath
-Wl,/home/micha/dev/aqbanking/aqbanking-svn/src/libs/aqbanking/.libs
-L/home/micha/dev/aqbanking/aqbanking-svn/src/libs/aqbanking
/home/micha/dev/aqbanking/aqbanking-svn/src/libs/aqbanking/.libs/libaqbanking.so
-L/usr/lib -lssl -lcrypto -ldl /usr/lib/libktoblzcheck.so
/usr/lib/libgwenhywfar.so -Wl,-soname -Wl,de.so.0 -o .libs/de.so.0.0.0
[...]
... and similar for all other bankinfo plugins.
To me this looks like it should be possible to get rid of openssl in an
Aqbanking package without support for HBCI (as a first step).
Unfortunately I'm somewhat lost since I know very little about using
libtool and autotools.
So, any help is appreciated...
Yours
Micha
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
