OpenSSL const changes in public APIs

Heikki Toivonen <[email protected]>
Newsgroups gmane.comp.python.cryptography
Message-ID <[email protected]>
I just realized that latest M2Crypto does not compile against latest
OpenSSL due to const changes in OpenSSL public APIs.

I'd like to get your opinions on how to solve this:

a) change M2Crypto to expect the latest OpenSSL 0.9.7g APIs
b) #ifdef all the const differences based on OpenSSL version (I think
they have trickled the changes in several versions, so this would get
really messy and I don't especially like to test against several OpenSSL
versions)
c) something else

--
  Heikki Toivonen
signature.asc (application/pgp-signature, 249 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFCe7GMb8x8KoP+JuwRArH1AJ93tn2pWZ++qT7g8OFgaUIEKoXtPgCbBxQV
KSN/pfEe92A8dzp8XPOMSVs=
=hdlO
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.