I'm trying to make a new crypto engine.
Any application that tries to use my custom OpenSSL library that includes my
engine gives me an error trying to find an external library for my new engine
(it tries to locate /usr/lib/libhwrng.so, where hwrng is my engine), although
if I run a "
M, Catalin Vasile <cata.vas...@nxp.com> wrote:
>
>
> I'm trying to make a new crypto engine.
>
> Any application that tries to use my custom OpenSSL library that includes
> my engine gives me an error trying to find an external library for my new
> engine (it tries to loca
I'm trying to make a new crypto engine.
Any application that tries to use my custom OpenSSL library that includes my
engine gives me an error trying to find an external library for my new engine
(it tries to locate /usr/lib/libhwrng.so, where hwrng is my engine), although
if I run a "gr
.v>
jyothi.v> -Original Message-
jyothi.v> From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf
Of Matt Caswell
jyothi.v> Sent: Friday, November 13, 2015 5:14 PM
jyothi.v> To: openssl-dev@openssl.org
jyothi.v> Subject: Re: [openssl-dev] procedure for addin
Thanks Matt.
We will try.
Best regards
Jyothi
-Original Message-
From: openssl-dev [mailto:openssl-dev-boun...@openssl.org] On Behalf Of Matt
Caswell
Sent: Friday, November 13, 2015 5:14 PM
To: openssl-dev@openssl.org
Subject: Re: [openssl-dev] procedure for adding new engine
Hi Matt,
Very useful information.
I too agree with you that we need not have a new engine distribution.
I see some options like dynamic engines and static engine support.
If we have built a library with dynamic engine interface, how can we do speed
test using openssl speed command.
Thanks
On 13/11/15 11:16, Vemulapalli Jyothi wrote:
> Hi Matt,
>
> Very useful information.
>
> I too agree with you that we need not have a new engine distribution.
>
> I see some options like dynamic engines and static engine support.
>
> If we have built a library wi
On 12/11/15 18:21, Vemulapalli Jyothi wrote:
> Hi all,
>
>
>
> We would like to add a new engine registration to openssl.
>
>
>
> Can you please explain a procedure?
>
>
>
> When we gone through the code, we could find an engines di
Hi all,
We would like to add a new engine registration to openssl.
Can you please explain a procedure?
When we gone through the code, we could find an engines directory in openssl ,
but those files are not getting compiled.
Do we need to give some additional options. Can you please help
My understanding is as there are some similarities between my device and
cryptodev device, i may follow the cryptodev. Is it right? If we want to
take reference from any other engine iam not getting any similarity between
my engine and any one from already implemented. If i go through with pkcs11
On 15/05/15 12:47, Animesh Das wrote:
Hi,
I have a new hardware crypto engine. The device can be accessed from
user space application opening the device like /dev/mydevice. There
are also some IOCTLs which can be used from user space. I want to add
that device as one of the engines of
On Fri, 2015-05-15 at 17:17 +0530, Animesh Das wrote:
I have a new hardware crypto engine. The device can be accessed
from user space application opening the device like
/dev/mydevice. There are also some IOCTLs which can be used from
user space. I want to add that device as one of the
] On Behalf Of Jim Gibbons
Sent: Sunday, November 23, 2008 4:45 AM
To: openssl-dev@openssl.org
Subject: adding a new engine
Is there documentation and/or an example of this?
If this is a question better suited for the users group, please let me
know.
Thanks for your help
Is there documentation and/or an example of this?
If this is a question better suited for the users group, please let me
know.
Thanks for your help.
__
OpenSSL Project
Hi,
When adding a new engine to openssl, is it necessary to add an entry to
engine_internal_check in engine_list.c and rebuild, or is there some way to
dynamically add a new engine.
Thanks,
Diarmuid.
_
Get
From: "Diarmuid Oneill" [EMAIL PROTECTED]
diarmuidoneill When adding a new engine to openssl, is it necessary
diarmuidoneill to add an entry to engine_internal_check in
diarmuidoneill engine_list.c and rebuild, or is there some way to
diarmuidoneill dynamically add a new engine.
Geoff Thorpe wrote:
On Tue, 31 Oct 2000, Ben Laurie wrote:
Yes, your answer is satisfactory.
If I understand then I can't use openssl.exe main application for
testing my new engine
(of course after compilation of openssl with new engine features).
Exactly, and this is wrong
Geoff Thorpe wrote:
On Tue, 31 Oct 2000, Ben Laurie wrote:
BTW: Right now, all the existing engine implementations typically work
immediately without any "setup" beyond what they work out for themselves
before, during, or after initialisation.
Indeed, but its possible to imagine
Dr S N Henson wrote:
The idea behind this is that a simple engine aware application could
then just call ENGINE_load_config("filename.cnf") and forget about any
other details.
Would carve the way to store the engine configuration in stone...
By
Goetz
--
Goetz Babin-Ebell, TC TrustCenter
The idea behind this is that a simple engine aware application could
then just call ENGINE_load_config("filename.cnf") and forget about any
other details.
or you can encode the parameters into string and pass this string around.
file-based configuration is not always the best.
every engine
Dr S N Henson wrote:
The idea behind this is that a simple engine aware application could
then just call ENGINE_load_config("filename.cnf") and forget about any
other details.
The reason I suggested a handle instead of a filename was so that the
data could come from elsewhere.
Cheers,
Ben.
Ben Laurie wrote:
Dr S N Henson wrote:
The idea behind this is that a simple engine aware application could
then just call ENGINE_load_config("filename.cnf") and forget about any
other details.
The reason I suggested a handle instead of a filename was so that the
data could come from
On Tue, 31 Oct 2000, Libor Krystek wrote:
I'am creating new engine for other hardware. This hardware must be
initialized before using but for its initialization I need input some
parameters (e.g. hostname, username, password).
Function ENGINE_init(ENGINE *e) call engine function init
NGINEs available even though many of them won't be supported on your host
system (because of lack of drivers, vendor libraries, etc).
Does that answer your question?
Yes, your answer is satisfactory.
If I understand then I can't use openssl.exe main application for
testing my new engine
(of
Geoff Thorpe wrote:
On Tue, 31 Oct 2000, Libor Krystek wrote:
I'am creating new engine for other hardware. This hardware must be
initialized before using but for its initialization I need input some
parameters (e.g. hostname, username, password).
Function ENGINE_init(ENGINE *e) call
From: Ben Laurie [EMAIL PROTECTED]
ben Does that answer your question?
ben
ben Leaves me with one - if specific engines have to be initialised "by
ben hand", then we haven't got much in the way of abstraction, have we? Is
ben there a better way? Config files? External programs?
Depends on
Ben Laurie wrote:
Geoff Thorpe wrote:
On Tue, 31 Oct 2000, Libor Krystek wrote:
I'am creating new engine for other hardware. This hardware must be
initialized before using but for its initialization I need input some
parameters (e.g. hostname, username, password).
Function
Goetz Babin-Ebell wrote:
Ben Laurie wrote:
Geoff Thorpe wrote:
On Tue, 31 Oct 2000, Libor Krystek wrote:
I'am creating new engine for other hardware. This hardware must be
initialized before using but for its initialization I need input some
parameters (e.g. hostname
Richard Levitte - VMS Whacker wrote:
From: Ben Laurie [EMAIL PROTECTED]
ben Does that answer your question?
ben
ben Leaves me with one - if specific engines have to be initialised "by
ben hand", then we haven't got much in the way of abstraction, have we? Is
ben there a better way?
u can still look around the various
ENGINEs available even though many of them won't be supported on your host
system (because of lack of drivers, vendor libraries, etc).
Does that answer your question?
Yes, your answer is satisfactory.
If I understand then I can't use openssl.exe m
On Tue, 31 Oct 2000, Ben Laurie wrote:
Yes, your answer is satisfactory.
If I understand then I can't use openssl.exe main application for
testing my new engine
(of course after compilation of openssl with new engine features).
Exactly, and this is wrong and bad. We should fix
31 matches
Mail list logo
