I should also add that printing the error stack doesn't yield much info
other than "you dun goof'd":
===================
First connection, client closes connection as excepted.
===================
BIO_set_fd with 4|1 #Socket 4, BIO_CLOSE
SSL_set_accept_state
SSL_accept
SSL_accept failed, SSL_get_error: 1 #SSL_ERROR_SSL
140059505588032:error:1408F119:SSL routines:ssl3_get_record:decryption
failed or bad record mac:../ssl/record/ssl3_record.c:375:
SSL_shutdown
SSL_clear
===================
Second connection, client suddenly blocks, has to be interrupted
with CTRL + C.
===================
BIO_set_fd with 5|1 #Socket 5, BIO_CLOSE
SSL_set_accept_state
SSL_accept
SSL_accept failed, SSL_get_error: 1 #SSL_ERROR_SSL
140059505588032:error:140A4044:SSL routines:SSL_clear:internal
error:../ssl/ssl_lib.c:559:
SSL_shutdown
SSL_clear
===================
Third connection, client blocks again, has to be interrupted again.
===================
BIO_set_fd with 4|1 #Socket 4, BIO_CLOSE
SSL_set_accept_state
SSL_accept
SSL_accept failed, SSL_get_error: 1 #SSL_ERROR_SSL
140059505588032:error:140A4044:SSL routines:SSL_clear:internal
error:../ssl/ssl_lib.c:559:
SSL_shutdown
SSL_clear
The error messages are being generated by ERR_print_errors_fp(stderr);
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users