Hi Geoff,
Is anyone working on adding DES support to the engine code?
Bill Hymas
IBM Linux Technology Center / IBM Global Services
Heidelberg, Germany
Geoff Thorpe <[EMAIL PROTECTED]> on 22-04-2001 04:40:58 AM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: Maurice Gittens <[EMAIL PROTECTED]>
Subject: Re: integrating engine driver into openssl
Hi there,
Sorry for the late reply, but there's been a problem with the mail-delivery
to
the developers (something went a bit berko with "openssl.org" DNS
settings).
Anyway, I'm copying and pasting this "quote" from a web-based mail archive
:-)
Future mail should be working OK though!
Maurice Gittens wrote:
> I've implemented an openssl engine driver for a cryptographic hardware
> device.
> Now that the driver seems to work I'm wondering what procedures should be
> followed to have it integrated into openssl.
Have you tried it with the latest openssl snapshots? There's been quite a
bit of
stuff I've dumped in there over the last couple of days that you may want
to
hook your ENGINE up with. It would also be cool if you could figure out any
parameterisable bits (like shared-library paths, etc) and integrate it with
the
"cmd_defns" stuff that's there now. That would save us time integrating
your
code in.
Other than that, all you need to do is to send one/some of us a copy of the
code
to poke and prod at. It would also help to provide any information on what
it's
for, as well as explanations for anything esoteric (eg. if it does anything
weird - why?). It will need to be self-contained, so any external
declarations
(eg. headers) need to be provided for inclusion also. For this reason, any
commercial elements would also need to be accompanied by some kind of a
waiver
to acknowledge that we can include, license, and maintain the code under
the
same banner as all the rest of the OpenSSL code (ie. no additional
licensing
requirements, restrictions on what we can/can't do with the code, etc).
"Commercial elements" includes any hardware API references from vendors or
others having copyright, and the ENGINE implementation itself too if it was
not
done and given freely from voluntary resources. :-)
Also, there's some major ENGINE improvements on the way soon (hopefully)
that
may render some of the above mute if you think "giving code without strings
attached" may pose any problems. Anyway, mail me directly if you want more
info
on any of this; licensing, past or future ENGINE changes, etc.
Regards,
Geoff
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
