Stunnel 4.33 released

The ChangeLog entry: Version 4.33, 2010.04.05, urgency: MEDIUM: * New features - Win32 DLLs for OpenSSL 1.0.0. This library requires to c_rehash CApath/CRLpath directories on upgrade. - Win32 DLLs for zlib 1.2.4. - Experimental support for local mode on WIN32 platform. Try exec =

Symmetric algorithms with Cell architecture

Is there anyone working with symmetric algorithms in Cell platform, i want suggestions to work with AES, taking advantage of the IBM Cell SPUs Thanks in advance smime.p7s Description: S/MIME cryptographic signature PGP.sig Description: This is a digitally signed message part

RE: OpenSSL on IBMi

OK, one step forward. I guess that previously you had a path error because you need to create a link (correctly) to point to your gmake program. And the CCSID of the delivered tools package is unimportant - it's the CCCSID of the unpacked programs that is important. Hmmm. Message ID . . . .

Re: OpenSSL on IBMi

I am able to narrow down on the icc option that is causing the problem. icc -c temp1/abc.c -o abc.o QAPTL/ICC: Unexpected exception MCH3601 $ icc -o abc.o -c temp1/abc.c $ So, specifying -c option before -o option (which is the case while compiling openssl) results in error. If I swap

RE: OpenSSL on IBMi

-c is an option, not an argument, so I think you'll find that the problem is that icc is objecting to the file-to-be-compiled is not at the end of the command line - i.e. is it looking for a - character in temp1/abc.c and failing. So: icc -c -o abc.o temp1/abc.c ... would also work. Like I

RE: OpenSSL on IBMi

Hmm, my version of icc works with the default syntax, for example: icc -I. -I.. -I../include -DOPENSSL_THREADS -D_MULTI_THREADED -v -v -O4 -DB_ENDI AN -DCHARSET_EBCDIC -DEBCDIC_500 -DNO_SYS_PARAM_H -D_ALL_SOURCE -DNO_SYSLOG -qTG TRLS=V5R1M0 -qTGTCCSID=500 -qTERASPACE=*YES *TSIFC -c cryptlib.c

Strange SSL_shutdown() error return (SSL_ERROR_SYSCALL but errno == 0)

Hello, While testing Python's SSL support with OpenSSL = 0.9.8m, we have encountered a strange error return from SSL_shutdown on a non-blocking socket (note: this is a different problem from the one described by Victor Stinner in an earlier thread last month). Basically: - SSL_shutdown(ssl

Building on freebsd sparc64

I noticed a problem when building openssl-1.0.0 on my sparc64 FreeBSD 9-CURRENT system. While building in crypto/des/, it failed with: m4 -B 8192 asm/des_enc.m4 des_enc-sparc.S m4: illegal option -- B usage: m4 [-d flags] [-t name] [-gs] [-D name[=value]]... [-U name]... [-I

X509_STORE reuse

Can I reuse an X509_STORE for multiple ssl connections, cert verifications etc, or should I create a fresh one for each operation? If I reuse it will it continue to grow as it pulls in more certificates? -- Chris Bare ch...@bareflix.com

SSL algorithms vs. all algorithms...

http://cvs.openssl.org/chngview?cn=19536 -SSL_library_init() only registers ciphers. Another important initialization -is the seeding of the PRNG (Pseudo Random Number Generator), which has to -be performed separately. +SSL_library_init() mainly adds ciphers and digests used directly by

Re: SSL algorithms vs. all algorithms...

On Tue, Apr 06, 2010, Victor Duchovni wrote: http://cvs.openssl.org/chngview?cn=19536 -SSL_library_init() only registers ciphers. Another important initialization -is the seeding of the PRNG (Pseudo Random Number Generator), which has to -be performed separately.

Re: SSL algorithms vs. all algorithms...

On Tue, Apr 06, 2010 at 09:17:01PM +0200, Dr. Stephen Henson wrote: Has the guidance to developers who use OpenSSL for TLS/SSL rather than as general-purpose cryptography toolkit changed wrt. library initialization? [...] I suppose it makes sense to add the SHA2 algorithms to