"make test" error for release 1.0.2n

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

"make test" error for release 1.0.2n

Porter, Andrew
My "make test" for today's 1.0.2n release is getting an error at the very last (I think)
"test_bad_dtls" step. This is FIPS-enabled, built with the 2.0.12 FIPS module. With the
Previous 1.0.2m release the "test_bad_dtls" step silently completed but with 1.0.2n I get:

test_bad_dtls
../util/shlib_wrap.sh ./bad_dtls_test
test_fatalerr
../util/shlib_wrap.sh ./fatalerrtest ../apps/server.pem ../apps/server.pem
SSL_accept() failed -1, 1
47220303776416:error:140800FF:SSL routines:ssl3_accept:unknown state:s3_srvr.c:869:
make[1]: Leaving directory `/data1/xd/openssl-1.0.2n/test'
OPENSSL_CONF=apps/openssl.cnf util/opensslwrap.sh version -a
OpenSSL 1.0.2n-fips  7 Dec 2017
built on: reproducible build, date unspecified
platform: linux-x86_64
options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx)
compiler: gcc -I. -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
-DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2
-DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
 -I/usr/local/ssl/fips-2.0/include -DRC4_ASM -DSHA1_ASM -DSHA256_ASM
 -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM
 -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM

Probably I don't care, since my application isn't using DTLS, but I'd just like a confirmation
that this is OK.

- Thanks, Andrew Porter
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Reply | Threaded
Open this post in threaded view
|

Re: "make test" error for release 1.0.2n

Matt Caswell-2


On 07/12/17 16:55, Porter, Andrew wrote:

> My "make test" for today's 1.0.2n release is getting an error at the very last (I think)
> "test_bad_dtls" step. This is FIPS-enabled, built with the 2.0.12 FIPS module. With the
> Previous 1.0.2m release the "test_bad_dtls" step silently completed but with 1.0.2n I get:
>
> test_bad_dtls
> ../util/shlib_wrap.sh ./bad_dtls_test
> test_fatalerr
> ../util/shlib_wrap.sh ./fatalerrtest ../apps/server.pem ../apps/server.pem
> SSL_accept() failed -1, 1
> 47220303776416:error:140800FF:SSL routines:ssl3_accept:unknown state:s3_srvr.c:869:
> make[1]: Leaving directory `/data1/xd/openssl-1.0.2n/test'
> OPENSSL_CONF=apps/openssl.cnf util/opensslwrap.sh version -a
> OpenSSL 1.0.2n-fips  7 Dec 2017
> built on: reproducible build, date unspecified
> platform: linux-x86_64
> options:  bn(64,64) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx)
> compiler: gcc -I. -I.. -I../include  -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN
> -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2
> -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m
>  -I/usr/local/ssl/fips-2.0/include -DRC4_ASM -DSHA1_ASM -DSHA256_ASM
>  -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM
>  -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
>
> Probably I don't care, since my application isn't using DTLS, but I'd just like a confirmation
> that this is OK.

This is coming from "test_fatalerr" not "test_bad_dtls". This question
came up on the openssl-dev list as well. I'll give the same answer I
gave there:

The 1.0.2 test framework is very noisy (its much better in 1.1.0). There
are a whole bunch of tests that output "failures" and "errors" which are
actually normal operation (because they are testing failure and error
conditions). The above is normal output from a successful test. The
important thing is if the overall "make test" process completes
successfully or exits with an error.

Matt

--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users