About non-blocking IO

2007-03-16 Thread Robin Redeker
Hello! I've spend some time on fixing the Perl openssl binding Net::SSLeay for non-blocking IO usage. I was working on the requirement of passing the same arguments to SSL_read and SSL_write on retries. Then someone told me that he read the openssl code (i guess it was the latest version), and

Re: [openssl.org #1451] PATCH (Re: Cross compile OpenSSL in Linux using MinGW32)

2007-03-16 Thread Alon Bar-Lev via RT
Hello, I don't exactly undersand the maintenance model of OpenSSL. I would really like to see a milestone set for this issue (http://rt.openssl.org/Ticket/Display.html?id=1451). We are waiting for this so that user will not be forced to patch OpenSSL in order to cross compile it. I will be

[openssl.org #1507] crash

2007-03-16 Thread via RT
This transaction appears to have no content __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager

RE: About non-blocking IO

2007-03-16 Thread David Schwartz
When an SSL_read() operation has to be repeated because of SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE, it must be repeated with the same arguments. I'm having a hard time to understand the openssl code to confirm that SSL_read doesn't need the same buffer on retries. And on the

bug report : Possible issue in AES asm code?

2007-03-16 Thread Erik de Castro Lopo
Hi all, I'm trying to track down a bug in my own code using valgrind and I've found something that I though I should report. If I configure openssl-0.9.8e using: ./Configure linux-elf -DPURIFY -ggdb and valgrind my program I get a couple of these reports: ==8577== Invalid write of