I am trying to use openssl 0.9.8 libs for SSL based
application development. I am facing a strange issue.
Whenever connection is rest on client side with RST
message from client to server, server is closed
abonrmally due to some memory corruption.
If I replace SSL calls with norms BSD socket calls
I have problem with signature verification:
When I try to verify the SMIME signed message (hello.txt.p7m - see
attachment) with the command:
openssl smime -verify -in hello.txt.p7m -inform DER -CAfile ca-bundle.crt -out
/dev/null
I obtain the following error message:
Verification failure
12491:e
Hey all -
I am having some troubling creating .so when linking against openssl
0.9.8. I do not encounter the problem when linking against openssl
0.9.7g. The error appears to be specific to x86_64. The system is a
EMT64 processor.
As an example, when linking against a stub that calls
SSL_libra
How do I access the client certificate and private key
from an SSL_CTX?
It was previously loaded into the SSL_CTX with
SSL_CTX_use_certificate() and
SSL_CTX_use_PrivateKey().
Thanks for the help,
-David
__
Do You Yahoo!?
Tired of spam? Yahoo! Ma
Oh Hi Steven,
I am pleasently surprised to see that you are monitoring the list.
Thanks for the changes in wcecompat. I downloaded your latest version
and I also had to make two minor changes for my environment. I'm not
sure how motivated you are to actually incorporate them In any
case, a
ld -soname libtest.so -shared -o libtest.so test.o
-L/usr/src/1.3.33/openssl-0.9.8 --whole-archive -lssl -lcrypto
-no-whole-archive
First of all I'd recommend to use gcc -shared even to link shared
objects. Not that this would remedy the "R_X86_64_PC32 is no good for
shared object," it's just
I downloaded openssl-0.9.8-stable-SNAP-20050805 and compiled it for my
Windows CE platform and had a few problems.
Sometimes "test latest snapshot" *really* means "*latest*":-)
1. In the CFLAGS define, the compiler didn't like the /wd4959. It
said it was unrecognized and refused to go further
Steven,
I've put a new wcecompat.zip up at essemer.com.au which includes ENOMEM and
EAGAIN. The remainder of the problems need to be corrected in OpenSSL.
Do you number wcecompat releases? I mean I'd like to mention some
reference point in INSTALL.WCE, e.g. "at least version x.y" or
"downlo
On 8/9/05, Andy Polyakov <[EMAIL PROTECTED]> wrote:
> What were your %INCLUDE% and %LIB% upon nmake time?
C:\tmp\newwcecompat\wcecompat>set
CC=clarm.exe
CFG=none
include=C:\Windows CE Tools\WCE420\POCKET PC 2003\include\ARMV4I;C:\Windows CE T
ools\WCE420\POCKET PC 2003\MFC\include;C:\Windows CE T
On Tue, Aug 09, 2005, Peter BENKO,VSE IT
Sluzby,+421-55-610-2045,+421-903-855532 wrote:
> I have problem with signature verification:
>
> When I try to verify the SMIME signed message (hello.txt.p7m - see
> attachment) with the command:
> openssl smime -verify -in hello.txt.p7m -inform DER -CAfi
I am implemeting CRL support in an application on
Solaris using OpenSSL 0.9.6d 9 May 2002.
According to the information I have gathered, CRL
support is not available in pre-0.9.7 OpenSSL
releases.
I have the opportunity to easily upgrade to 0.9.7g.
Will 0.9.7g provide the suport necessary for
in
3. In bf_skey, memcpy was undefined,
Will look into it...
Looked into it and it didn't make any sense. Required header file is
included so it shouldn't be a problem... Strangely enough there're a
number of files calling memcpy, which are compiled prior bf_skey.c, so
how come it gets "angry"
Hi Andy,
The first release wasn't numbered. This new release is numbered 1.1.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Polyakov
Sent: Wednesday, 10 August 2005 3:29 AM
To: openssl-users@openssl.org
Subject: Re: openssl-0.9.8-stable-SNAP-2005
The file "C:\Program Files\Microsoft eMbedded C++
4.0\EVC\wce420\bin\WCEARMV4.BAT" should contain a line like:
if "%WCEROOT%"=="" set WCEROOT=C:\Program Files\Microsoft eMbedded
C++ 4.0
Which is obviously customised on install since the default is "C:\Microsoft
eMbedded C++ 4.0" and I cho
Whoops, I missed the memcpy reference in the original post. I added a
memcpy prototype to string.h in wcecompat 1.1 to satisfy an OpenSSL 0.9.8
compile problem, so I guess this is the one. The problem with the wcecompat
approach is that it overrides/replaces the Microsoft supplied header files.
I
I wrote wcecompat solely for the OpenSSL port (but with a view to using it
for other things), so I guess you could say I'm more of an OpenSSL-er than a
Windows CE-er.
Do you know if a similar change needs to be made for ARMV4T?
I believe your include problem below relates to the possible install
Hello Richard,
--- Richard Levitte - VMS Whacker
<[EMAIL PROTECTED]> escribió:
> In message
>
<[EMAIL PROTECTED]>
> on Tue, 9 Aug 2005 03:45:01 +0200 (CEST), Johnny
> Gonzalez <[EMAIL PROTECTED]> said:
>
> johnnygonzalezl> > Hmm, maybe you should ask the
> OpenCA folks? They
> johnnygonzalezl>
In message <[EMAIL PROTECTED]> on Wed, 10 Aug 2005 03:27:23 +0200 (CEST),
Johnny Gonzalez <[EMAIL PROTECTED]> said:
johnnygonzalezl> > Hmm? It should, in the engines/ directory.
johnnygonzalezl> Well, I don't know if I did it wrong, but I didn't
johnnygonzalezl> find the libraries in the downloa
18 matches
Mail list logo
