AES_CCM has a real well duh! type bug on systems where long is 32 bits.
The compiler will probably tell you where it is.
Sorry - fix it a couple of days.
Peter
Peter Waltenberg
__
OpenSSL Project
Hi,
Since ChangeCipherSpec is not of handshake message type, the handshake
message sequence number should not be incremented. Only the record level
sequence number shall be incremented.
Proposed patch attached modifies both the TX side and the RX side.
Thanks,
Alex
Hi,Since ChangeCipherSpec is
Darryl Miles wrote:
David Schwartz wrote:
If I'm misunderstanding the man page and/or the source code
please speak up.
My man page says:
If the underlying BIO is non-blocking, SSL_shutdown() will also
Yes but what SSL_shutdown() actually does is always return 0
This discussion a
Nanno Langstraat wrote:
So I can add one more voice to the choir: the current SSL_shutdown() API
appears to give trouble to every non-blocking developer (I remember I
lost serious time noticing + tracking down this 100% CPU bug), and
afterwards things still don't really work right.
I can't
Darryl Miles wrote:
2) SSL_read() already has a return value -1/ZERO_RETURN which indicates
end-of-stream. You may then call SSL_shutdown() to look to see if 1 is
returned or not. Or even SSL_get_shutdown() and take whatever security
action your application needs to take in the event of an
