Which operating system, version of OpenSSL, and version of the CryptoSwift
software? I'll check it out.
Lynn Gazis
-Original Message-
From: Kevin Babcock [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 5:22 PM
To: [EMAIL PROTECTED]
Subject: engine error w/ cswift
I am unable t
I am unable to verify the Verisign/RSA Secure Server CA certificate
when using the Cryptoswift card. It works fine when I turn off the
hardware acceleration. As far as I can tell, all other certificates
verify properly.
$ ./openssl verify -verbose -engine openssl -CApath ../certs \
From: Jeffrey Altman <[EMAIL PROTECTED]>
jaltman> > The definition of MD() is in rand_lcl.h. It's a macro. What has
jaltman> > changed is the definition of EVP_Digest()...
jaltman>
jaltman> Ok. Next obvious question. What should MD() become?
See the commit I did an hour and a half ago. Bas
> Ah, I forgot a make update... Doing it now.
great
> The definition of MD() is in rand_lcl.h. It's a macro. What has
> changed is the definition of EVP_Digest()...
Ok. Next obvious question. What should MD() become?
Jeffrey Altman * Sr.Software Designer C-Kermit 7.1 Alpha availab
I'd like to make a question to the developers about the new ASN.1 code.
For some projects in which we are involved, we added new structures using
the old code.
Now I looked briefly at the new code in the snapshots and I realized
that many things are changing (with big improvements IMHO reading REA
From: Jeffrey Altman <[EMAIL PROTECTED]>
jaltman> perl util\mkdef.pl 32 libeay > ms\libeay32.def
jaltman> Warning: ASN1_GENERALSTRING_free does not have a number assigned
jaltman> Warning: ASN1_GENERALSTRING_it{1} does not have a number assigned
jaltman> Warning: ASN1_GENERALSTRING_new does not h
perl util\mkdef.pl 32 libeay > ms\libeay32.def
Warning: ASN1_GENERALSTRING_free does not have a number assigned
Warning: ASN1_GENERALSTRING_it{1} does not have a number assigned
Warning: ASN1_GENERALSTRING_new does not have a number assigned
Warning: CONF_set_nconf does not have a number assigned
> Did you modify the configuration scripts to set up the single library or =
> did you just edit the makefiles directly? That is the issue I am looking =
> into now. (If you have anything you want to share, we'd love to see it.)
After building openssl normally, we run the following script. Note t
Did you modify the configuration scripts to set up the single library or
did you just edit the makefiles directly? That is the issue I am looking into
now. (If you have anything you want to share, we'd love to see it.)
Verdon Walker(801) 861-2633[EMAIL PROTECTED]Novell Inc., the
leading pro
On Tue, Jul 10, 2001 at 11:47:01AM +0200, Götz Babin-Ebell wrote:
>> The distribution file names are:
>>
>> o openssl-0.9.6b.tar.gz [normal]
>> o openssl-engine-0.9.6b.tar.gz [engine]
> Could you start signing such mails ?
>
> And please, include a hash for the distribution files
From: Götz Babin-Ebell <[EMAIL PROTECTED]>
babinebell> Could you start signing such mails ?
Yes, I could. I will keep it in mind for next time.
babinebell> And please, include a hash for the distribution files.
babinebell> Server can be hacked and this is a security sensitive area...
The curr
Richard Levitte wrote:
Hello Richard,
> As a few people noticed, not only was the announcement of OpenSSL 0.9.6b sent
> more than once (due to, eh, technical error...), but the version number was
> 0.9.6a everywhere in the message body!
Shit happens...
> OpenSSL version 0.9.6b released
> =
12 matches
Mail list logo
