> [julien.ca...@c-s.fr - Wed Jun 02 22:12:07 2010]:
>
> I'm currently working on ECDSA, and use OpenSSL for tests. I also use
> BouncyCastle to verify the validity of PKCS10 request.
> I have been able to generate a PKCS10 with a HSM that BouncyCastle
> rejects but OpenSSL verifies. At first I t
Hello,
I'm currently working on ECDSA, and use OpenSSL for tests. I also use
BouncyCastle to verify the validity of PKCS10 request.
I have been able to generate a PKCS10 with a HSM that BouncyCastle
rejects but OpenSSL verifies. At first I thought it was BouncyCastle
that was mistaken, but afte
>> Recently, mingw64 has chosen to be compatible with MSVC's symbol decoration
>> conventions, ie no underscore for x64 dll's. The underscore assumption has
>> been made in one file (afaik), namely:
>>
>> x86_64-xlate.pl: line 83: if ($flavour eq "mingw64") { $gas=1; $elf=0;
>> $win64=1; $prefix="_
> Please remove the error "nasm is an unrecognized ..." by applying the
> attached patch to VC-32.pl
Addressed in http://cvs.openssl.org/chngview?cn=19691. Thanks for report. A.
__
OpenSSL Project
On Wed, Jun 2, 2010 at 6:31 PM, Dr. Stephen Henson wrote:
> On Wed, Jun 02, 2010, Arunkumar Manickam wrote:
>
> > Hi,
> >
> > with openssl 1.0, x509_vfy.c, check_cert function loops in to issue
> > callback get_crl on a condition ctx->current_reasons != CRLDP_ALL_REASONS
> .
> >
> > Can some one
On Wed, Jun 02, 2010, Arunkumar Manickam wrote:
> Hi,
>
> with openssl 1.0, x509_vfy.c, check_cert function loops in to issue
> callback get_crl on a condition ctx->current_reasons != CRLDP_ALL_REASONS .
>
> Can some one explain what is the use of CRLDP_ALL_REASONS and who should set
> ctx->cur
Hi,
with openssl 1.0, x509_vfy.c, check_cert function loops in to issue
callback get_crl on a condition ctx->current_reasons != CRLDP_ALL_REASONS .
Can some one explain what is the use of CRLDP_ALL_REASONS and who should set
ctx->current_reasons to CRLDP_ALL_REASONS in case a get_crl callback ha
Although I knew PVK is supported... Could not find how to use it...
Tested on snapshot of 20100602.
openssl-1.0.0-pvk-usage.patch
Description: Binary data
At ssl_lib.c:331, SSL_new() allocates s->param:
s->param = X509_VERIFY_PARAM_new();
if (!s->param)
goto err;
X509_VERIFY_PARAM_inherit(s->param, ctx->param);
Later in the function, s->method->ssl_new() is called:
if (!s->method->ssl_new(s))
The X509_VERIFY_PARAM_new() function looks like this in 1.0.0:
X509_VERIFY_PARAM *X509_VERIFY_PARAM_new(void)
{
X509_VERIFY_PARAM *param;
param = OPENSSL_malloc(sizeof(X509_VERIFY_PARAM));
memset(param, 0, sizeof(X509_VERIFY_PARAM));
x509_verify_param_zero(p
10 matches
Mail list logo