Hello,
I have been looking at the OpenSSL source code, and this jumped out as a
possible error. 'n¹ is an unsigned before it is passed into ssl3_read_n,
which causes the worry of an overflow. To prevent this, I added check that
just makes sure that n is not less than zero, which wouldn't
On Thu, Jul 10, 2014 at 11:26:46AM +0200, Chaney, Benjamin via RT wrote:
Hello,
I have been looking at the OpenSSL source code, and this jumped out as a
possible error. 'n?? is an unsigned before it is passed into ssl3_read_n,
which causes the worry of an overflow. To prevent this, I
Running the applications in this way is not supported. Closing this ticket.
Matt
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Hi,
Using OpenSSL 1.0.1h 5 Jun 2014, a DTLS client can't negotiate ECC-based
ciphersuites with a compliant DTLS server since it fails to send the relevant
extensions mandated by RFC 4492.
% openssl s_client -dtls1 -debug
CONNECTED(0003)
write to 0x1761c50 [0x176c160] (166 bytes = 166 (0xA6))
On 10/07/2014 21:28, The default queue via RT wrote:
Everything works fine if -dtls1_1 is used instead of -dtls1.
Err, I meant works with -tls1_1 (TLS) instead of -dtls (DTLS).
Manuel.
__
OpenSSL Project
On Wed Jul 09 16:24:04 2014, lull...@yahoo.com wrote:
Hi,
openssl enc command with -aes-xxx-xts doesnt work if an IV is specified
When you say it doesn't work, what do you mean? Do you get an error? If so
what is it?
as below:
openssl enc -engine af_alg -aes-256-xts -in plaintext_file
On Thu Jul 10 11:26:46 2014, bcha...@akamai.com wrote:
Hello,
I have been looking at the OpenSSL source code, and this jumped out as a
possible error. 'n¹ is an unsigned before it is passed into ssl3_read_n,
which causes the worry of an overflow. To prevent this, I added check that
just makes
