Hi,
You're right, an OPENSSL_assert() is not an appropriate error handling here.
The connection should just be terminated with an alert. I have submitted patch
#2625 to change this. Thanks for the report!
Best regards
Robin
On Oct 13, 2011, at 1:42 AM, zhu qun-ying wrote:
Hi,
While
' : segment must be defined
using #pragma data_seg or code_seg prior to use
NMAKE : fatal error U1077: 'cl' : return code '0x2'
Stop.
***
FIPS BUILD FAILURE*
***
C:\work\openssl-fips-2.0-test-20111019
The openssl-1.0.1-stable-20111019 build fails as follows:
fips_premain.c
link /nologo /subsystem:console /opt:ref /debug /dll /map /base:0xFB0 /out:o
ut32dll\libeay32.dll /def:ms/LIBEAY32.def @C:\DOCUME~1\zkrr01\LOCALS~1\Temp\nmb0
2032.
LIBEAY32.def : error LNK2001: unresolved external
On Wed, Oct 19, 2011 at 4:48 PM, Kenneth Robinette
supp...@securenetterm.com wrote:
The openssl-1.0.1-stable-20111019 build fails as follows:
fips_premain.c
link /nologo /subsystem:console /opt:ref /debug /dll /map /base:0xFB0
/out:o
ut32dll\libeay32.dll /def:ms/LIBEAY32.def
@C
The current default openssl.cnf appears to have default_bits = 1024:
http://cvs.openssl.org/fileview?f=openssl/apps/openssl.cnfv=1.23.4.6
however, NIST has recommended avoiding reliance on 1024-bit RSA keys
after 2010.
See pages 63-66 of:
As some of you may be aware the new Oracle SPARC T4 processor has
hardware crypto support just like its predecessors SPARC T1,T2,T3.
However unlike the prior SPARC T series processors the hardware crypto
is not hyper-privileged but is instead new instructions accessible from
unprivileged
hi, there:
i want to add a set of new ciphers to the openssl--1.0.0d source code and
make it as my default ssl cipher-suite.
(a EC asymmetric cipher named SM2, a symmetric cipher named SM1, and a
digest cipher SM3.)
now i have implemented SM1,SM2,SM3 in crypto/evp, and test it ok.
i'm trying
