Nicolas Pelloux-Prayer wrote:
I'm currently working on a similar task during the development of a
TLS client (with client-side authentication), using a PKCS#11 hardware
token.
The main problem we encountered is that we cannot access the private
key stored in the token; Therefore we made an en
Yes, what ever attempts are made to improve the documentation, they should
probably start with errors and omissions in this book, rather than from scratch.
Perhaps O'Rielly might want to publish a followup?
-Original Message-
From: owner-openssl-us...@openssl.org on behalf of Mark
Sent:
>>OpenSSL artifacts that are created by the application, then handed to
>>some other part of the API for use, so who is now responsible for the
>>destructions of them? That kind of misunderstanding.
>>Darryl
Hi Darryl,
To an extent you are correct. We have fixed the issue and it is due to o
experimental support to HEAD. This seems to decrypt the example OK
> and can decrypt its own output. It adds a new option -pwri_password to the
> cms utility (will need something better at some point).
EXCELLENT ! This works on my machine:
tar xvfz openssl-SNAP-20091127.tar.gz
cd openssl
Thanks, will try it out as soon as I can.
Regards,
Jun Han
> Date: Thu, 26 Nov 2009 13:24:29 +0100
> From: st...@openssl.org
> To: openssl-users@openssl.org
> Subject: Re: Adding a custom engine to OpenSSL
>
> On Thu, Nov 26, 2009, Loke Jun Han wrote:
>
> >
> > Hi,
> >
> >Is there a
Yup.
> From: open...@morethan.org
> To: openssl-users@openssl.org
> Subject: Re: Adding a custom engine to OpenSSL
> Date: Thu, 26 Nov 2009 05:21:35 -0600
>
> On Thu November 26 2009, Loke Jun Han wrote:
> >
> > Hi,
> >
> >Is there anyway to for openSSL to automatically load a specifi
Forwarded to openssl-users for public discussion.
Best regards,
Lutz
- Forwarded message from Xavier De Kepper -
From: Xavier De Kepper
To: "r...@openssl.org"
Date: Fri, 27 Nov 2009 02:15:17 -0800
Subject: Question on SSL_shutdown timeout
Thread-Topic: Question on SSL_shutdown
Hi All,
> Rene Hollan wrote:
> >
> > Oh, you need to dig deeper, to understand the semantics and
> not just
> > the syntax of those APIs.
> >
> > I didn't say using the source as documentation was
> convenient, but it
> > is possible, to any degree of detail you want.
> >
> > To wit: given th
I'm currently working on a similar task during the development of a TLS
client (with client-side authentication), using a PKCS#11 hardware token.
The main problem we encountered is that we cannot access the private key
stored in the token; Therefore we made an engine which implements RSA
signature
