Re: 64-bit OpenSSL for Darwin/Mac OS X?

2006-07-13 Thread Kyle Hamilton
If any of them say 'fail', it's not good stuff. If make returns anything other than 0, it's not good stuff. Otherwise, it's good stuff. :) -Kyle H - Original Message - From: "Martin Simmons" <[EMAIL PROTECTED]> To: Sent: Thursday, July 13, 2006 12:34 PM Subject: 64-bit OpenSSL for Da

[openssl.org #1066] bug: smime -sign from non-seekable input does not work with DER and PEM output formats

2006-07-13 Thread Stephen Henson via RT
[EMAIL PROTECTED] - Wed May 11 17:37:29 2005]: > Current snapshots (checked on 20050503 and 20050511) and 0.9.7e do not > work when asked to sign non-seekable input. 0.9.6c in Debian woody > (package version 0.9.6c-2.woody.7) does work. > > That is, > > echo hello|openssl smime -sign -inkey pr

64-bit OpenSSL for Darwin/Mac OS X?

2006-07-13 Thread Martin Simmons
Hi there, Is there any official support for 64-bit OpenSSL for Darwin/Mac OS X? With the attached patch, I've managed to compile the 0.9.8b source on Mac OS 10.4.6 with Xcode 2.2 using: ./Configure shared darwin-ppc64-cc It seems to work for simple HTTP and certificate operations. I also ran m

[openssl.org #1363] segmentation fault in TSA test on FreeBSD 6.1 on Opteron

2006-07-13 Thread Stephen Henson via RT
Don't have that platform to test on. However from the stack dump: #0 0x000800d6e466 in memcpy () from /lib/libc.so.6 #1 0x000800770a5e in asn1_ex_i2c (pval=0x61d708, cout=0x61d708 "IxMVoXDTA5MDcxMjE2MjIxMVowRDELMAkGA1UEBhMCSFUx\nETAPBgNVBAgTCEJ1ZGFwZXN0MRQwEgYDVQQKEwtHb3YtQ0EgTHRkLj

[openssl.org #1363] segmentation fault in TSA test on FreeBSD 6.1 on Opteron

2006-07-13 Thread Artem Chuprina via RT
FreeBSD 6.1, Opteron, gcc (GCC) 3.4.4 [FreeBSD] 20050518 OpenSSL HEAD of 2006-06-12 19:10 UTC configured with MAKEFLAGS=-- ./config -g shared zlib Manual deletion of -O3 flag from Makefile eliminates the segfault. Changing to -O2 does not. make test's output ended with: Response has been gener

[Patch] th-lock.c

2006-07-13 Thread Gisle Vanem
There should be no reason to typecast the argument to CRYPTO_set_locking_callback(): diff -u3 -Hb -r openssl-SNAP-20060713\crypto\threads\th-lock.c crypto\threads\th-lock.c --- openssl-SNAP-20060713\crypto\threads\th-lock.c Fri Mar 21 18:15:34 2003 +++ crypto\threads\th-lock.c Thu Jul 13 15:08

Re: IPv6 support in openssl's BIO

2006-07-13 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Thu, 13 Jul 2006 15:59:18 +0200, Jan Pazdziora <[EMAIL PROTECTED]> said: jpr-ossl> OK. I suggest I prepare a patch that will not change them (they will jpr-ossl> be IPv4-only), will mark them with #ifndef OPENSSL_NO_DEPRECATED, and jpr-ossl> will not add them to

[Patch] test-programs

2006-07-13 Thread Gisle Vanem
to surpress warnings. Patches attached. --gv diff -u3 -Hb -r openssl-SNAP-20060713\crypto\bf\bf_opts.c crypto\bf\bf_opts.c --- openssl-SNAP-20060713\crypto\bf\bf_opts.c Fri Nov 28 13:00:09 2003 +++ crypto\bf\bf_opts.c Thu Jul 13 15:58:35 2006 @@ -59,7 +59,7 @@ /* define PART1, PART2, PART3 or PART4

Re: IPv6 support in openssl's BIO

2006-07-13 Thread Jan Pazdziora
On Thu, Jul 13, 2006 at 02:08:22PM +0200, Richard Levitte - VMS Whacker wrote: > > Note that they are documented by being declared in bio.h. The OpenSSL OK. > documentation in form of .pod files isn't complete yet. > > The best thing to do with functions that you want removed is to wrap > them

Re: IPv6 support in openssl's BIO

2006-07-13 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Thu, 13 Jul 2006 13:39:22 +0200, Jan Pazdziora <[EMAIL PROTECTED]> said: jpr-ossl> On Thu, Jul 13, 2006 at 12:32:50PM +0200, Richard Levitte - VMS Whacker wrote: jpr-ossl> > In message <[EMAIL PROTECTED]> on Thu, 13 Jul 2006 11:15:59 +0200, Jan Pazdziora <[EMAI

Re: IPv6 support in openssl's BIO

2006-07-13 Thread Jan Pazdziora
On Thu, Jul 13, 2006 at 12:32:50PM +0200, Richard Levitte - VMS Whacker wrote: > In message <[EMAIL PROTECTED]> on Thu, 13 Jul 2006 11:15:59 +0200, Jan > Pazdziora <[EMAIL PROTECTED]> said: > > jpr-ossl> The primary concern is a change in API/ABI, namely removal of three > jpr-ossl> functions: BI

[openssl.org #1362] BF_encrypt crash

2006-07-13 Thread via RT
When i am running my application using openSSL it crashes in the following steps gsamain!BF_encrypt+0x4ce gsamain!BF_cbc_encrypt+0x1f8 gsamain!bf_cbc_cipher+0x29 gsamain!tls1_enc+0x209 gsamain!do_ssl3_write+0x214 gsamain!ssl3_write_bytes+0xd0 gsamain!ssl3_write+0x108 gsamain!SSL_write+0x72 gsam

[openssl.org #1361] PATCH: Adding IPv6 support to s_client and s_server

2006-07-13 Thread Jan Pazdziora via RT
Hello, attached please find a patch that makes it possible to use IPv6 addresses with openssl's s_client and s_server. The patch is against openssl-0.9.8b as found in the Fedora Core Rawhide openssl-0.9.8b-3.src.rpm package. Without this patch, using IPv6-only hostname fails with $ ope

Re: IPv6 support in openssl's BIO

2006-07-13 Thread Richard Levitte - VMS Whacker
In message <[EMAIL PROTECTED]> on Thu, 13 Jul 2006 11:15:59 +0200, Jan Pazdziora <[EMAIL PROTECTED]> said: jpr-ossl> The primary concern is a change in API/ABI, namely removal of three jpr-ossl> functions: BIO_get_host_ip, BIO_get_port, and BIO_gethostbyname. They jpr-ossl> are not documented in

IPv6 support in openssl's BIO

2006-07-13 Thread Jan Pazdziora
Hello, as part of an effort to support IPv6, we are now ready to provide patches for openssl to replace IPv4-only routines and structures (gethostbyname, char ip[4], sockaddr_in) by a more generic and AF-agnostic ones. The IPv6 issues are being logged in a bug https://bugzilla.redhat.com