Libor Krystek wrote:
>
> Geoff Thorpe wrote:
> >
> > ENGINE_ctrl();
> >
> > make your "init()" handler fail (setting an explanatory error) unless
> > ENGINE_ctrl() has already been called to pass in everything you need.
> >
> > ENGINE_init() is used to get a "functional" reference, not just a
> > "structural" one. Eg. ENGINE_by_id() returns only a structural reference -
> > so using that you can call ENGINE_ctrl() to initialise whatever you need.
> > It is only when a structural reference is required that the ENGINE's
> > "init" handler will be called to try and make the ENGINE actually get
> > ready to work. This typically happens by calling ENGINE_init() directly,
> > or something implicit like "ENGINE_set_default()" that requires the ENGINE
> > be "working". For structural references, the ENGINE's own functions are
> > never called - that's so that you 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 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 it.
Cheers,
Ben.
--
http://www.apache-ssl.org/ben.html
"There is no limit to what a man can do or how far he can go if he
doesn't mind who gets the credit."
Robert Woodruff
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
