This is a discussion on problem with PEM_read_SSL_SESSION when upgrading from 0.9.7 to 0.9.8g - Openssl ; --Yylu36WmvOXNoKYn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all! I've recently been put in charge of SSL, and I'm working my way through the= O'Reilly book. However, I'm a bit stumped as to this problem. I tried to upgrade ...
Content-Type: text/plain; charset=us-ascii
I've recently been put in charge of SSL, and I'm working my way through the=
However, I'm a bit stumped as to this problem.
I tried to upgrade our build system to use OpenSSL 0.9.8g, and thought I su=
However, the code is blowing up. The code is for caching sessions, and it =
is roughly as follows:
var =3D PEM_read_SSL_SESSION(session_file, NULL, NULL, const_cast
The compiler message is as follows:
=2E.. passing `char * (*)()' as argument 1 of `PEM_ASN1_read(void * (*)(voi=
d **, const unsigned char **, long int), const char *, FILE *, void **, int=
(*)(char *, int, int, void *), void *)'
Well, clear as mud, right? Looks like this is how the former calls PEM_ASN=
#define PEM_read_SSL_SESSION(fp,x,cb,u) (SSL_SESSION *)PEM_ASN1_read( \
(char *(*)())d2i_SSL_SESSION,PEM_STRING_SSL_SESSION,fp,( char **)x,cb,u)
I don't see that I have any control over the first argument of PEM_ASN1_rea=
nor do tweaking the various arguments affect anything. I'm beginning to th=
that I've got something including an older version of the openssl headers, =
may well happen if they #include a file which no longer exists in 0.9.8g, s=
the older OpenSSL revs will be on the include path.
Does anyone have any insight into this?
The stream is deaf, yet sings its melody for all to hear.
For a good time on my email blacklist, email firstname.lastname@example.org.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (OpenBSD)
-----END PGP SIGNATURE-----
OpenSSL Project http://www.openssl.org
User Support Mailing List email@example.com
Automated List Manager firstname.lastname@example.org