In message <[EMAIL PROTECTED]> on Sat, 18 Oct 2003 21:39:46 +0200, Stefan Olsson <[EMAIL PROTECTED]> said:The idea was to have the application support both atalla and the default openssl engine. The choice will be done in a config file. To conclude: If the config says "openssl" then we should not issue any ENGINE calls at all. When config says "atalla" we load that engine (or all of them) and then place ENGINE calls.
stefan> Richard Levitte - VMS Whacker wrote:
stefan> stefan> >Either ENGINE_load_builtin_engines() (if you want to maximise the
stefan> >potential of using any supported hardward that happens to be
stefan> >available) or ENGINE_load_atalla(). And what exactly is the identity
stefan> >you give ENGINE_by_id()?
stefan> >
stefan> > stefan> >
stefan> I tried to use the ENGINE_load_builtin_engines() call and that
stefan> gives the same problem, if I try to set e = ENGINE_by_id("openssl")
stefan> the call will fail. However if I add ENGINE_load_openssl(); it
stefan> works but gives the TEST_ENG_OPENSSL_RC4_P_INIT message...
I suspected that's what you did. However, ENGINE_by_id("openssl") will not give you the Atalla engine, it will only give you that OpenSSL test engine. To get the Atalla engine, use "atalla", like this:
e = ENGINE_by_id("atalla");
Thanks for all your help!
Brgds
/Stefan
-- If you make people think they're thinking, they'll love you; but if you really make them think they'll hate you.
smime.p7s
Description: S/MIME Cryptographic Signature
