Thanks Andy. It looks like that was indeed the problem -- my copy of the
CVS tree had gotten out of sync somehow.
On Mon, Dec 12, 2011 at 7:29 AM, Andy Polyakov ap...@openssl.org wrote:
I'm still having this build problem on Windows, with code just pulled
from CVS 1.0.1 stable branch. It
as it has
apparently changed since I first reported this.
Any assistance, please?
Thanks,
Tyrel
On Mon, Nov 28, 2011 at 9:45 AM, Tyrel Haveman tyr...@gmail.com wrote:
I'm running the following commands on Windows with the latest code from
the 1.0.1 branch:
set FIPSDIR=..\dep
perl Configure fips
Sorry, it is still line 966 of mk1mf.pl.
On Fri, Dec 9, 2011 at 9:32 AM, Tyrel Haveman tyr...@gmail.com wrote:
I'm still having this build problem on Windows, with code just pulled from
CVS 1.0.1 stable branch. It happens when building the 32-bit build on a
64-bit OS.
Note that I can build
I'm running the following commands on Windows with the latest code from the
1.0.1 branch:
set FIPSDIR=..\dep
perl Configure fips no-hw VC-WIN32 --prefix=c:\devel\openssl\out
call ms\do_nasm
The do_nasm script runs:
perl util\mkfiles.pl 1MINFO
perl util\mk1mf.pl nasm VC-WIN32 1ms\nt.mak
I've been having a problem for a while now but haven't been able to look at
it until now. Here's what I do on Linux:
Download the latest fips-2.0 snapshot (openssl-fips-2.0-test-20111031
currently), and extract, then CD into the dir.
$ export FIPSDIR=~/fipstemp
$ ./config
$ make
$ make install
$
It looks like there's a failure in the FIPS module 2.0 self tests on Windows
currently. It happens on both x86 and AMD64. The failure is in the integrity
check. Complete output of fips_test_suite.exe is below.
FIPS-mode test application
FIPS 2.0-dev unvalidated test module xx XXX
...@openssl.org wrote:
From: Dr. Stephen Henson st...@openssl.org
Subject: Re: FIPS self-tests failing on Windows
To: openssl-dev@openssl.org
Date: Tuesday, September 6, 2011, 3:22 PM
On Tue, Sep 06, 2011, Tyrel Haveman
wrote:
It looks like there's a failure in the FIPS module 2.0
That may be the case, but it fixed my problem nevertheless.
On Tue, Sep 6, 2011 at 7:43 PM, Dr. Stephen Henson st...@openssl.orgwrote:
On Tue, Sep 06, 2011, John Foley wrote:
Is this Windows 7? Try adding the FIXED flag to the Microsoft linker.
Windows 7 will relocate DLLs (quite often).
On the 1.0.1 branch, libeay.num hasn't been updated for quite some time,
which is now resulting in a build failure on Windows. Here are the warnings
about the missing definitions:
Warning: CRYPTO_ccm128_aad does not have a number assigned
Warning: CRYPTO_ccm128_decrypt does not have a number
A recent change (within the last 3 days I think) seems to have broken
the build of the FIPS module on 64-bit Windows. Here's the relevant
output:
--
set ASM=nasm -f win64 -DNEAR -Ox -g
perl crypto\bn\asm\modexp512-x86_64.pl
This works. Thanks Andy.
On Fri, Aug 12, 2011 at 2:26 PM, Andy Polyakov ap...@openssl.org wrote:
A recent change (within the last 3 days I think) seems to have broken
the build of the FIPS module on 64-bit Windows. Here's the relevant
output:
--
set
Thank you, Andy, this works great! Also thanks for fixing it so quickly.
Tyrel
On Sun, Aug 7, 2011 at 11:02 AM, Andy Polyakov ap...@openssl.org wrote:
The error happens in fips_aes_selftest.c, lines 157-159:
if (memcmp(tag, ccm_tag, sizeof(ccm_tag))
|| memcmp(out, ccm_ct,
OK
Signature DSA test started
Signature DSA test OK
POST Failed
Power-up self test failed
On Fri, Aug 5, 2011 at 4:08 AM, Dr. Stephen Henson st...@openssl.orgwrote:
On Thu, Aug 04, 2011, Tyrel Haveman wrote:
Is there someone in particular who would
Hello,
After building the FIPS module on Windows using the do_fips.bat script, I
run the fips_test_suite.exe. On most machines all tests succeed. But on one
machine I have, the CCM test fails (exact error below). I did a bit of
debugging and it looks like the functions are simply returning the
Is there someone in particular who would be optimal to look into this? I
have no knowledge of the code or algorithm in question here.
Tyrel
On Thu, Aug 4, 2011 at 4:48 PM, Dr. Stephen Henson st...@openssl.orgwrote:
On Thu, Aug 04, 2011, Tyrel Haveman wrote:
Hello,
After building
take a look at this. It started
happening, I believe, when this file was added: crypto/bn/asm/
modexp512-x86_86.pl
Thanks,
Tyrel
On Mon, Jul 11, 2011 at 4:12 PM, Dr. Stephen Henson st...@openssl.orgwrote:
On Mon, Jul 11, 2011, Tyrel Haveman wrote:
Hello again,
We've noticed now that while
, Jun 30, 2011 at 4:07 PM, Tyrel Haveman ty...@binarypeople.netwrote:
Ah, okay. We tried that out and the FIPS module does build great
afterwards. But then, later, the 1.0.1 fips-capable build fails to
build with this reasoning:
nasm -f win64 -DNEAR -Ox -g -o tmp32dll\rc4-x86_64.obj
to Configure.
Can someone take a look?
Thanks!
Tyrel
On Wed, Jun 29, 2011 at 2:14 PM, Steve Marquess
marqu...@opensslfoundation.com wrote:
On 06/29/2011 04:46 PM, Dr. Stephen Henson wrote:
On Wed, Jun 29, 2011, Tyrel Haveman wrote:
Thanks Steve. This helps a lot. One more related question: Why
Henson st...@openssl.org wrote:
On Thu, Jun 30, 2011, Tyrel Haveman wrote:
We just noticed that building the fips module on Linux works fine with
no-asm, but on a 64-bit Windows build, it doesn't work without no-asm.
Here's the error:
link /nologo /subsystem:console /opt:ref /debug
$SEH_begin_RC4_set_key' undefined
tmp32dll\rc4-x86_64.asm:756: error: symbol `L$SEH_end_RC4_set_key' undefined
NMAKE : fatal error U1077: 'C:\devel\crypto\tools\nasm.EXE' : return code '0x1'
Stop.
On Thu, Jun 30, 2011 at 2:28 PM, Dr. Stephen Henson st...@openssl.org wrote:
On Thu, Jun 30, 2011, Tyrel
AM, Dr. Stephen Henson st...@openssl.org wrote:
On Tue, Jun 28, 2011, Tyrel Haveman wrote:
All,
I'm having a problem when building OpenSSL 1.0.1 along with fips-2.0.
My layout is like this:
/home/tyrel/openssl-test/openssl -- contains the 1.0.1 branch from CVS
/home/tyrel/openssl-test
All,
I'm having a problem when building OpenSSL 1.0.1 along with fips-2.0.
My layout is like this:
/home/tyrel/openssl-test/openssl -- contains the 1.0.1 branch from CVS
/home/tyrel/openssl-test/fips -- contains the extract fips-2.0
snapshot tarball
My build steps are (from the openssl-test
22 matches
Mail list logo
