It would appear that the opensll-0.9.8q.tar.gz file is corrupt.
un-tar fails.
Cheers,
Brent
The tarball doesn't appear to be corrupted for me, what errors are you getting?Under Redhat EL4 and EL5 VMs,tar zxf openssl-0.9.8q.tar.gz, works perfectly fine for me. Original Message From: Brent Evans brent.ev...@gmail.comTo: openssl-users@openssl.orgSent: Fri, Dec 3, 2010, 8:48
Hi,
There is no problem with the archive.
If you are under Windows, use the latest 7zip (version 9.20). You will
get a warning but the decompression is OK. The previous version of 7zip
had a limitation for tar support.
Cheers,
--
Mounir IDRASSI
IDRIX
http://www.idrix.fr
On 12/3/2010 2:28
That's a pretty bold statement and doesn't always apply in a product
environment.
I have not deployed 1.0.0b (because of the pending issues); I'm still at 1.0.0a
and have to decide whether to patch the vulnerabilities, or risk updating
OpenSSL completely and retesting all of its consumers.
On Fri, Dec 03, 2010 at 09:50:49AM -0500, Erik Tkal wrote:
That's a pretty bold statement and doesn't always apply in a product
environment.
I have a production environment. The non-security issues in the unpatched
1.0.0b release create substantial interoperability issues with servers
and
I rebuild OpenSSL and didn't get a capi.dll. I'm using 0.9.8k. Is there
something I'm missing in the build process that I need to change to get
the engines to compiled in. From what I've read it looks like it builds
these engines into the openssl dlls.
The following returns still NULL for me.
Victor
I am still have issues with
the default ECDH parameters in 1.0.0c.
The key generation with NIST Prime-Curve P-192 crashes.
static void nist_cp_bn(BN_ULONG *buf, BN_ULONG *a, int top)
{
int i;
BN_ULONG *_tmp1 = (buf), *_tmp2 = (a);
for (i = (top); i != 0; i--)
*_tmp1++ =
Ok, so I realized if I run Configure with no-static-engine I'll get the
separate dlls. These are the commands I run
C:\Documents and Settings\tfili\Desktop\openssl-0.9.8kperl Configure
VC-WIN32 --prefix=c:\temp\openssl no-static-engine
ms\do_ms.bat
nmake -f ms\ntdll.mak
Unfortunately I now get
On Fri, Dec 03, 2010, Fili, Tom wrote:
I rebuild OpenSSL and didn't get a capi.dll. I'm using 0.9.8k. Is there
something I'm missing in the build process that I need to change to get
the engines to compiled in. From what I've read it looks like it builds
these engines into the openssl dlls.
Hi,
In order to enable the CAPI engine, you have to use the enable-capieng
switch : this will compile the CAPI engine statically inside OpenSSL.
Here is a example of configure command line for this : perl Configure
VC-WIN32 --prefix=c:/openssl enable-capieng
I hope this will help.
Cheers,
--
On Fri, Dec 03, 2010 at 09:10:41AM -0800, Marcus Carey wrote:
I am still have issues with the default ECDH parameters in 1.0.0c.
kEECDH handshakes appear to work.
The key generation with NIST Prime-Curve P-192 crashes.
How do you reproduce this?
static void nist_cp_bn(BN_ULONG *buf,
Sorry to use this list for this.
But I have tried every way I know to get off the list suggestions??
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Mounir IDRASSI
Sent: Friday, December 03, 2010 1:04 PM
To:
openssl ecdhtest
openssl s_server
Must use the -no_ecdhe flag.
openssl.exe s_server -no_ecdhe
ecdhetest.exe has the same access violation
Unhandled exception at 0x004222f6 in ecdhtest.exe: 0xC005: Access
violation reading location 0x0001
openssl.exe!nist_cp_bn(unsigned int *
Go to http://www.openssl.org/support/community.html
Erik Tkal
Juniper OAC/UAC/Pulse Development
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Richard Buskirk
Sent: Friday, December
Ok, I got it loading. Thanks.
I'm still have an issue, which would stem from my lack of understanding
of OpenSSL. This seems to succeed in giving me the private key.
ENGINE_load_builtin_engines();
if( ENGINE *e = ENGINE_by_id(capi) )
{
if( ENGINE_init(e) )
{
On Fri, Dec 03, 2010 at 12:06:22PM -0800, Marcus Carey wrote:
openssl ecdhtest
What is openssl ecdhtest?
Must use the -no_ecdhe flag.
openssl.exe s_server -no_ecdhe
With what cert/key? Any other options? What client invocation? ...
openssl.exe!nist_cp_bn(unsigned int * buf=0x00acea80,
Hello,
We use openssl with libcurl to programmatically access, upload to and
download from various URL's using https, ftps, and smtps protocols. We
can successfully perform our tasks on UNIX/Linux and Windows boxes,
including Solaris on SPARC and Intel, Linux, etc. However, we
consistently
Hello,
We use openssl with libcurl to programmatically access, upload to and download
from various URL's using https, ftps, and smtps protocols. We can successfully
perform our tasks on UNIX/Linux and Windows boxes, including Solaris on SPARC
and Intel, Linux, etc. However, we consistently
I am implementing a two-party messages exchange system based on CMS
for Liberté Linux (http://dee.su/liberte).
The command-line argument -md to openssl cms -sign_receipt is
apparently ignored, and the default digest algorithm (SHA-1 in my
tests) is used instead. In addition, the -noattr argument
I used openssl to create a server certificate and key. The s_server
application never
loads because the error occurs using the default ECDH parameters. Then I
ran the ecdhtest application to see if there was a problem.
ecdhtest.exe is the test application in the crypto/ecdh directory for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
how are you.
me that I will begin to prepare for Christmas,...
conserne in the code,
I brought a lot of code changes is a bit more solid at the moment
especially the server that I think is fulfilling its function. I work on
the client and I can not
Hi,
What compiler are you using under Windows?
From my side, I have compiled and tested binaries produced by VC++ 2008
SP1 (cl version 15.00.30729.01) and the latest standalone native MinGW
(gcc 4.5.0), and in both cases everything is OK (no crash and all tests
succeed)
--
Mounir IDRASSI
On Fri, Dec 03, 2010 at 01:43:17PM -0500, Victor Duchovni wrote:
I don't understand the code in BN_nist_mod_192(), which calls
nist_cp_bn(), it has rather obscure pointer manipulation:
/*
* we need 'if (carry==0 || result=modulus) result-=modulus;'
* as comparison
23 matches
Mail list logo
