On Thu, 15 Jun 2000, Richard Levitte - VMS Whacker wrote:
> From: Geoff Thorpe <[EMAIL PROTECTED]>
>
> geoff> Perhaps however, the UI_METHOD could be formulated independently
> geoff> (./crypto/ui/) but bound into the ENGINE framework in the same way that
> geoff> RSA, DSA, etc are - so that an ENGINE can if it wishes supply a UI_METHOD,
> geoff> to be set as a default, eg. in a call to ENGINE_set_default(e,
> geoff> ENGINE_METHOD_ALL), or just made available to be used selectively.
>
> I like the thought of a UI_METHOD, but I fail to see what an ENGINE
> would do with it... Or are you thinking of possible devices with
> their own little keyboard?
Well, whatever really ... the hardware may have a strange nature, do
biometrics, or just want to ask weirder questions than normal code would.
As it's C-code at the first layer that is hooking in, it can either just
handle "user"-input differently, or could even communicate with the device
itself to get *it* to ask questions (, or both). The benefit of using a
UI_METHOD is that, if the caller/application knows what they/it are/is
doing, they can plug in their own UI_METHOD to tweak things (eg. the
remote admin thing I suggested in my post).
Dunno, thinking out loud. What other angles might there be ... hmmm ...
Cheers,
Geoff
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
