Python's SSL module (built on OpenSSL) would improperly handle null bytes in
the SubjectAltName field domain name, deferring the validation code to other
fields. This has been patched on their end, but may be indicative of a bug in
OpenSSL. The unpatched code used OpenSSL's GENERAL_NAME_print()
Hi,
xmm6 and xmm7 registers are not correctly restored on bn_scatter5 return.
The diff was generated using git HEAD.
I am using openssl-1.0.1e that contains the bug. On openssl git logs it
appears the bug is present since the first commit when bn_scatter5 was
implemented.
regards,
Oscar
On Tue Dec 03 21:35:13 2013, afels...@cisco.com wrote:
However, I'm uncertain as to how appropriate is this use
of GENERAL_NAME_print(). Is the intent of this function to be used
for purposes like this, or is it intended more for human-readable
output, or something else entirely?
The outputs
Update ppc-xlate.pl to remove the register prefixes v and vs. For
example, v0 and vs0 are both converted to 0.
---
crypto/perlasm/ppc-xlate.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/crypto/perlasm/ppc-xlate.pl b/crypto/perlasm/ppc-xlate.pl
index c075d5f..118da16
A new Linux ABI, called ELFv2, was created for the little-endian PPC64
platform. It includes several changes to the current ABI and affects
mainly how functions are called between modules/objects. Functions
descriptors are not used in the new ABI and this patch updates how the
directives .globl
Thank you. That clarifies things.
-Original Message-
From: Stephen Henson via RT [mailto:r...@openssl.org]
Sent: Tuesday, December 03, 2013 3:51 PM
To: Andrew Felsher (afelsher)
Cc: openssl-dev@openssl.org
Subject: [openssl.org #3188] Bug Report Null bytes in SubjectAltName mishandled
Hi,
xmm6 and xmm7 registers are not correctly restored on bn_scatter5 return.
The diff was generated using git HEAD.
I am using openssl-1.0.1e that contains the bug. On openssl git logs it
appears the bug is present since the first commit when bn_scatter5 was
implemented.
Good catch.
