So I have to do the following steps (I use Win2000,
with CYGWIN):
1) gunzip the patch-file :
"pkcs11.openssl.adnovum.20010615.patch.gz" in : /cygwin/user/tmp/
directory
2) download the file : openssl-SNAP-20010613.tar.gz
(the one the above patch refer to)
3) gunzip the above file in the s
Hi there,
Sorry I haven't piped up before, but I've been too busy to contribute
anything of worth to the discussion.
On Wednesday 16 January 2002 12:15, Dr S N Henson wrote:
> Eric Laroche wrote:
> > Querying capabilities (PKCS#11 calls them 'mechanisms') is already
> > implemented in the code'
Eric Laroche wrote:
>
> Dr S N Henson wrote:
> >
> >Eric Laroche wrote:
> >>
> >> Yes, I am aware of the OpenSSL engine interface. Our code applies
> >> quite similar mechanisms of feeding 'configuration' information (name/
> >> value pairs) from application code. However, the engine command
>
Paolo Rossi wrote:
>
> You wrote me this on last October (see besides)
>
> I'm asking you what I've to do in order to install and use this new version
> of patch.
The new 2001/12/12 patch contains the C source files and header files
that make up the crypto/pkcs11/ directory.
Small adjustments
Dr S N Henson wrote:
>
>Eric Laroche wrote:
>>
>> Yes, I am aware of the OpenSSL engine interface. Our code applies
>> quite similar mechanisms of feeding 'configuration' information (name/
>> value pairs) from application code. However, the engine command
>> definitions affect the whole engine
hange '-'/'+' line pairs
accordingly.
In the specific patch, changes are done mainly on makefiles, and some
code is added to ssl/ssl_rsa.c.
Hope this helps.
Regards,
Eric
----
----------
- Original Message -
Eric Laroche wrote:
>
> Hi,
>
>
> Yes, I am aware of the OpenSSL engine interface. Our code applies
> quite similar mechanisms of feeding 'configuration' information (name/
> value pairs) from application code. However, the engine command
> definitions affect the whole engine setting, whereas
Eric Laroche wrote:
>
> Hi,
>
>
> Yes, I am aware of the OpenSSL engine interface. Our code applies
> quite similar mechanisms of feeding 'configuration' information (name/
> value pairs) from application code. However, the engine command
> definitions affect the whole engine setting, whereas
Richard Levitte wrote:
>
>From: "Steven Reddie" <[EMAIL PROTECTED]>
>
>smr> Richard, that was Zoran from Eracom and myself (as a Computer
>smr> Associates employee). We never got together, but Zoran did
>smr> submit his code. I put my submission on the back-burner long
>smr> enough that I think
From: "Steven Reddie" <[EMAIL PROTECTED]>
smr> Richard, that was Zoran from Eracom and myself (as a Computer
smr> Associates employee). We never got together, but Zoran did
smr> submit his code. I put my submission on the back-burner long
smr> enough that I think it's irrelevant now. I still ha
s like it works in
a similar way to my own code.
Steven
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Richard Levitte - VMS
Whacker
Sent: Thursday, 13 December 2001 8:10 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [PATCH] PKCS#11 code u
Hi,
Richard Levitte wrote:
>
>From: Eric Laroche <[EMAIL PROTECTED]>
>
>Eric.Laroche> The token object specification format has been widened.
>Eric.Laroche> It is now more powerful and more intuitive, using
>Eric.Laroche> name/value pairs, e.g.:
>Eric.Laroche> "pkcs11:library=cryptoki&tokenlabel
From: Eric Laroche <[EMAIL PROTECTED]>
Eric.Laroche> The token object specification format has been widened.
Eric.Laroche> It is now more powerful and more intuitive, using
Eric.Laroche> name/value pairs, e.g.:
Eric.Laroche> "pkcs11:library=cryptoki&tokenlabel=eric&objectlabel=two&dologin=true"
Hi developers,
I reworked some of our (AdNovum's) previously posted OpenSSL PKCS#11
code. Code robustness has been enhanced and the code is (so I hope)
clearer, and better layered (into a core PKCS#11 part and a PKCS#11
token object finding (keys, certs) part).
The object finding logic has bee
14 matches
Mail list logo
