[openssl-dev] SNAPSHOT updates

2015-03-13 Thread The Doctor
What is happening? In the Moutain Time Zone: It was at 22:22 MST then 23:22 MDT then 00:22 MDT !! -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising!

[openssl-dev] [openssl.org #3748] do_name_ex in crypto/asn1/a_strex.c does not treat case 0 in XN_FLAG_SEP_MASK

2015-03-13 Thread Peter Sylvester via RT
Hi, when a single -nameopt utf8 or others is used in openss x509 or others, the separator mask is 0. This preempts the command as soon as the Issuer is formatted. It seems that the case 0 should be treated lin the same ways as XN_FLAG_SEP_CPLUS_SPC Best Peter Sylvester

Re: [openssl-dev] Suspicious crash in 1.0.2

2015-03-13 Thread Erik Forsberg
Hi, Matt. I have not seen this committed to master or 1.0.2 yet ? Another person complained about it too, so its probably good idea to get it checked in. Patch works fine for all my use cases. -- Original Message -- On 28/02/15 06:53, Erik Forsberg wrote: Hi. I seem to have run into a

Re: [openssl-dev] [openssl.org #3745] OpenSSl Bug, affected release 0.9.8zd

2015-03-13 Thread Steve Schefter
On 3/13/2015 4:00 PM, Rath, Santosh via RT wrote: But when I build the openssl with shared mode, then it is failing and reporting below errors. gcc: /home/ratsa02/openssl/openssl-fips-2.0.2/fips_binary/fipsfips_premain.c: No such file or directory gcc:

Re: [openssl-dev] Suspicious crash in 1.0.2

2015-03-13 Thread Matt Caswell
On 13/03/15 20:57, Erik Forsberg wrote: Hi, Matt. I have not seen this committed to master or 1.0.2 yet ? Another person complained about it too, so its probably good idea to get it checked in. Patch works fine for all my use cases. Hi Erik, Don't worry - I've not forgotten about it!!

Re: [openssl-dev] [openssl.org #3745] OpenSSl Bug, affected release 0.9.8zd

2015-03-13 Thread Rath, Santosh via RT
Thank you Stephen, Since the product is already build on openssl.0.9.8.r, and if we upgrade it to openssl0.1.1l then there could be lot of change in terms of API what our product use. And one more pain point is the product is using .so of libcrypto and libssl. But when I build the

[openssl-dev] [openssl.org #3745] OpenSSl Bug, affected release 0.9.8zd

2015-03-13 Thread Stephen Henson via RT
On Fri Mar 13 21:00:30 2015, santosh.r...@ca.com wrote: Thank you Stephen, Since the product is already build on openssl.0.9.8.r, and if we upgrade it to openssl0.1.1l then there could be lot of change in terms of API what our product use. Well if you'd used any OpenSSL 0.9.8 using ./config

Re: [openssl-dev] problems building openssl-1.0, 2 win64a binaries with vs2013 on windows 7

2015-03-13 Thread Jeremy Farrell
On 13/03/2015 22:10, Joey Yandle wrote: ... On side note the error is indication that your nasm is out-of-date and you are missing out some optimizations. I'm using the nasm-2.07 windows installer from sourceforge: http://sourceforge.net/projects/nasm/ Is there something more recent? The

Re: [openssl-dev] problems building openssl-1.0, 2 win64a binaries with vs2013 on windows 7

2015-03-13 Thread Joey Yandle
tmp32\aesni-sha256-x86_64.asm:113: error: symbol `__imp_RtlVirtualUnwind' undefined Can you confirm that attached patch addresses the problem? Yes, that fixes it. However, the build then fails during linking: lib /nologo /out:out32\libeay32.lib @C:\Users\dragon\AppData\Local\Temp\

Re: [openssl-dev] [openssl.org #3744] Enhancement Request

2015-03-13 Thread lists
On 03/11/2015 01:28 PM, Shawn Fernandes via RT wrote: Hi, At the moment, we have SSL handshake making use of a single certificate, using a single key-pair present in the certificate. In the event the MITM has the same certificate(SSL - offloader) then the data can be encrypted/decrypted.

[openssl-dev] do_name_ex in crypto/asn1/a_strex.c does not treat case 0 in XN_FLAG_SEP_MASK

2015-03-13 Thread Peter Sylvester
Hi, when a single -nameopt utf8 or others is used in openss x509 or others, the separator mask is 0. This preempts the command as soon as the Issuer is formatted. It seems that the case 0 should be treated lin the same ways as XN_FLAG_SEP_CPLUS_SPC Best Peter Sylvester