[openssl-dev] [openssl.org #3650] sha1-586.asm broken in 1.0.2-stable for Windows builds

2015-02-04 Thread Mark Andrews via RT
I am also having a issue this issue. It is a 32 bit build issue only. The 64 bit build completes using the same development environment. The offending instruction is "movd". Unfortunately I am not a x86 assembler expert. Mark perl crypto\sha\asm\sha1-586.pl win32 /MD /Ox /O2 /Ob2 -DO

[openssl-dev] [openssl.org #3686] doc/openssl-shared.txt - "No such file"

2015-02-04 Thread Rich Salz via RT
Thanks, fixed. commit 1f7103b6ebd1579e4ead17405f89d44330386949 Author: Rich Salz Date: Wed Feb 4 18:50:00 2015 -0500 Fix various build breaks TABLE wasn't updated from a previous Configure change Missed an RMD160/RIPE/RIPEMD unification in mkdef.pl Makefile install_sw referenced file doc/openss

Re: [openssl-dev] ms\version32.rc(47) : fatal error RC1004: unexpected end of file found

2015-02-04 Thread John Foley (foleyj)
Yes, it's working now. Thanks. Are you interested in receiving the build failure notification directly from our Jenkins server? Or would you rather I continue to forward the failures to Openssl-dev? > On Feb 4, 2015, at 6:40 PM, "Matt Caswell" wrote: > > > >> On 04/02/15 21:34, John Fole

Re: [openssl-dev] ms\version32.rc(47) : fatal error RC1004: unexpected end of file found

2015-02-04 Thread Matt Caswell
On 04/02/15 21:34, John Foley wrote: > Is anyone seeing the following error when building master on Windows? > > ms\version32.rc(47) : fatal error RC1004: unexpected end of file found > > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Windows > Kits\8.1\bin\x86\rc.EXE"' : return code '0x1

[openssl-dev] ms\version32.rc(47) : fatal error RC1004: unexpected end of file found

2015-02-04 Thread John Foley
Is anyone seeing the following error when building master on Windows? ms\version32.rc(47) : fatal error RC1004: unexpected end of file found NMAKE : fatal error U1077: '"C:\Program Files (x86)\Windows Kits\8.1\bin\x86\rc.EXE"' : return code '0x1' Stop. The full build log is located here: htt

Re: [openssl-dev] FIPS compliant digital signature

2015-02-04 Thread Rex Bloom
Thank you!! Worked perfectly and was exactly what I was missing. -Original Message- From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of Dr. Stephen Henson Sent: Wednesday, February 4, 2015 1:21 PM To: openssl-dev@openssl.org Subject: Re: [openssl-dev] FIPS compliant d

Re: [openssl-dev] FIPS compliant digital signature

2015-02-04 Thread Dr. Stephen Henson
On Wed, Feb 04, 2015, Rex Bloom wrote: > Can someone help me understand what type of digital signature I can use for > FIPS compliance. > > I used this command: > > openssl genrsa -aes128 -passout pass:mypassphrase -out privkey.pem 2048 > > to generate a pem file but when I tried to load this

[openssl-dev] FW: AlgorithmIdentifier validation issue and PATCH openssl 1.0.1k 1.0.1l 1.0.2

2015-02-04 Thread Blumenthal, Uri - 0558 - MITLL
On 1/29/15, 16:20 , "Blumenthal, Uri - 0558 - MITLL" wrote: >Certificates that are semantically correct but encoded by “obtuse” CA >(Apple in particular) fail to validate because they encode >AlgorithmIdentifier in two legal but slightly different ways. > >Until 1.0.1k OpenSSL code did not bother

[openssl-dev] FIPS compliant digital signature

2015-02-04 Thread Rex Bloom
Can someone help me understand what type of digital signature I can use for FIPS compliance. I used this command: openssl genrsa -aes128 -passout pass:mypassphrase -out privkey.pem 2048 to generate a pem file but when I tried to load this as follows: RSA *rkey = PEM_read_bio_RSAPrivateKe

[openssl-dev] [openssl.org #3688] Bug report; OpenSSL 1.0.2; Solaris 11.0; Sparc T4; evp_test core dumps

2015-02-04 Thread Göran Hammarbäck via RT
Hello, I am building openssl 1.0.2 on a number of platforms, and I am having problems on a virtual Solaris 11.0 machine running on a Sparc T4. The code builds fine, but the evp_test core dumps. Here are the last lines of output from the command (test/evp_test test/evptests.txt): Testing cipher id

Re: [openssl-dev] The evolution of the 'master' branch

2015-02-04 Thread Salz, Rich
> Not sure if my questions are already answered. But I'll go ahead and ask > them... All excellent questions. As Matt said, we don't know yet. > Or would there be the "public headers" for applications? And than the > "private headers" for version bound extensions that need to access the > inte

Re: [openssl-dev] Android 64-bit configure targets

2015-02-04 Thread Andy Polyakov
Hi, > I am currently building OpenSSL for Android with current NDK r10d. > > I notice the configure script only has targets for the 32bit Android ABIs. > > Are there plans to add the 64bit ABIs (arm64, x86-64 and mips64)? Yes. Currently plan is to have generic android64 and then specific for aa

[openssl-dev] Creating libssl.so and libcrypto.so for AIX

2015-02-04 Thread aixtools
Hi, To be compatible with the way IBM distributes openssl in /usr/lib/libssl.a and /usr/lib/libcrypto.a I would like to make the .so "archives" as well. Actually, these are archives in the 'ar' command sense, but become members of the archive. I have been trying to understand how Makefile.

Re: [openssl-dev] The evolution of the 'master' branch

2015-02-04 Thread Matt Caswell
On 04/02/15 06:51, Timo Teras wrote: > On Tue, 3 Feb 2015 17:02:31 -0500 > Rich Salz wrote: > >> As we've already said, we are moving to making most OpenSSL data >> structures opaque. We deliberately used a non-specific term. :) >> As of Matt's commit of the other day, this is starting to happe