Linking against system libraries
Florian Weimer <[email protected]>
| Newsgroups | gmane.comp.encryption.cryptlib |
|---|---|
| Message-ID | <[email protected]> |
As discussed in the other thread, cryptlib embeds code from other sources. The symbols have not been mangled, so there are symbol clashes. In other contexts, I've seen crashes because of zlib version mismatches. This can be avoided by linking against the system zlib, which appears to be straightforward. However, with OpenSSL's libcrypto, it's more difficult, and there appears to be an actual ABI change in crypt/des.h: DES_key_schedule has an additional member weak_key in the OpenSSL version. (The wrapping struct seems less of an issue at the ABI level.) This is actually used in a few places, including the random number generator. Is this known to cause problems in practice? -- Florian Weimer <[email protected]> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99 _______________________________________________ Cryptlib mailing list [email protected] via Mail: [email protected] Archive: ftp://ftp.franken.de/pub/crypt/cryptlib/archives/ http://news.gmane.org/gmane.comp.encryption.cryptlib Posts from non-subscribed addresses are blocked to prevent spam, please subscribe in order to post messages.