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 our build system to use OpenSSL 0.9.8g, and thought I succeeded. However, the code is blowing up. The code is for caching sessions, and it is roughly as follows: var = PEM_read_SSL_SESSION(session_file, NULL, NULL, const_cast<char *>(get_password_chars())); The compiler message is as follows: ... passing `char * (*)()' as argument 1 of `PEM_ASN1_read(void * (*)(void **, 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_ASN1_read: #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_read, nor do tweaking the various arguments affect anything. I'm beginning to think that I've got something including an older version of the openssl headers, which may well happen if they #include a file which no longer exists in 0.9.8g, since the older OpenSSL revs will be on the include path. Does anyone have any insight into this? -- <URL:https://www.subspacefield.org/~travis/> The stream is deaf, yet sings its melody for all to hear. For a good time on my email blacklist, email [EMAIL PROTECTED]
pgpvmV6jqEq67.pgp
Description: PGP signature
