ok I think I figured out one problem - the client side was using a cert
signed with a password protected key, which my script was unable to deal
with. Having fixed that, I am now getting error
140890B2 : SSL routines:SSL3_GET_CLIENT_CERTIFICATE:no certificate returned
on the server side.
and e
Thanks a lot, it helped, i had "multithreaded" C-Runtime.
As I see that's big difference between
"multithreaded" and "multithreaded dll"
- Original Message -
From: "Thomas Monjalon" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 12, 2003 2:49 PM
Subject: Re: BIO bug
Shema wrote:
Hello friends,
this bug exists from the earlier versions of OpenSSL
and the question is why it is not fixed yet? :)
Currently I am using openssl-0.9.7c.tar.gz.
So, this code crashes on any WIN32 platform,
Visual C++ 60 compiler:
{
BIO *bio;
char buf[] = "HELLO";
bio = BIO_new_fp(std
On Wed, Nov 12, 2003, Thitikorn Trakoonsirisak wrote:
> Hi
>
> I have sent mail to this mailing list to ask about how to set Issuing
> Distribution Point in CRL but there is no any answer. It is important for my
> work. I try to search documents in many webs but I can't find answer, so I
> send t
Hi all,
I tried to connect from my client ssl (Part of visibroker ORB SSL lib).
When connecting to OpenSSL, I get the following errors on the OpenSSL.
ERROR 18650:error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown
Any clues as to why I get the above error?
thanks,
-Sriram
Hi,
I used the following command to creat a signature.
"openssl dgst -sign -out "
However why the signature can not be verified using corresponding
self-signed certificate.
"openssl dgst -signature -verify "
What's wrong? Thanks.
ok never mind, got it working. My server certificate had expired.
Thanks for all your help.
Stella
On Wed, Nov 12, 2003 at 01:23:15PM +, Stella Power wrote:
> ok I think I figured out one problem - the client side was using a cert
> signed with a password protected key, which my script was u
Hi,I have a problem regarding the base-64 encoding.Base-64
encoding mandates to have a '\n' after every 64 bytes. For sending an
SCEP request, the transport protocol used is HTTP. It uses the GET
method and the "message" to the GET is the base64 encoded pkcs#7
request. Are there any functions av
Base-64 encoding mandates to have a '\n' after every 64 bytes.
No, it doesn't. It's common practice, but it's not required.
Add BIO_FLAGS_BASE64_NO_NL, as in
BIO_set_flags(your_bio_object, BIO_FLAGS_BASE64_NO_NL);
/r$
--
Rich Salz, Chief Security Architect
DataPower Technology
Please remove my id from user list
Id:[EMAIL PROTECTED]
.muralidharan
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Shema
Sent: Wednesday, November 12, 2003 7:01 PM
To: [EMAIL PROTECTED]
Subject: Re: BIO bug
Thanks a lot, it helped, i had "multithr
Title: Message
Please remove my id from maillisting thanks for
done.
id:[EMAIL PROTECTED]
muralidharan.
11 matches
Mail list logo