Hey there,
On Thu, 15 Jun 2000, Dr Stephen Henson wrote:
When I was discussing various methods of handling OpenSSL key databases
the issue of PIN handling came up and in more general UI handling wrt
"PIN like operations".
The problem is that OpenSSL PIN handling is all over the place. The
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,
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
Richard Levitte - VMS Whacker wrote:
Hello Richard,
From: Dr Stephen Henson [EMAIL PROTECTED]
drh So, any thoughts on the matter?
Could clear up some stuff...
Hmm, a general UI function in OpenSSL that takes the following
parameters:
I don't think that one UI function is a good solution:
From: Goetz Babin-Ebell [EMAIL PROTECTED]
gbe I don't think that one UI function is a good solution:
gbe There should be more than UI function:
gbe
gbe 1. InsertString: ask the user for a string
gbe 1.1InsertPass: special case: ask for a passphrase
gbe (1.2 InsertFile:
From: Goetz Babin-Ebell [EMAIL PROTECTED]
gbe Richard Levitte - VMS Whacker wrote:
gbe Hallo Richard,
gbe From: Goetz Babin-Ebell [EMAIL PROTECTED]
gbe gbe 1. InsertString: ask the user for a string
gbe gbe 1.1InsertPass: special case: ask for a passphrase
gbe gbe (1.2
Richard Levitte - VMS Whacker wrote:
Hallo Richard,
From: Goetz Babin-Ebell [EMAIL PROTECTED]
gbe Richard Levitte - VMS Whacker wrote:
gbe Agree,
gbe but a seperate function for user autentification would be good...
Exactly what do you mean? If it's the separation between strings,
When I was discussing various methods of handling OpenSSL key databases
the issue of PIN handling came up and in more general UI handling wrt
"PIN like operations".
The problem is that OpenSSL PIN handling is all over the place. The PEM
stuff has PIN callbacks applicable on a per call basis even
