On 2000-03-14 07:37:49 +0100, Richard Levitte - VMS
Whacker wrote:
> Personally I don't see the problem with getting the
> correct mime headers served by smime and just graft
> them in among all the others, but YMMV.
While this may be fine for the simplest applications, it's
not reasonable in a situation in which I want to generate
multiple signatures and put them into a multipart/mixed,
or in which I have a multipart/mixed and want to verify
multiple signatures with different back-ends. I don't
really want to do MIME en- and decoding just for passing
data to the crypto back-end, and back.
Additionally, it's an aesthetic question. Why put a MIME
engine into the crypto back-end when the front-end will do
MIME, probably has a better tested MIME parser, and
additionally the back-end produced MIME doesn't really fit
into the things the front-end wants to do?
> This has already been addressed, although it was
> possibly not part of OpenSSL 0.9.5. It is however
> there in the snapshot.
> The change that has been made doesn't just cover smime,
> but all applications that need a password. It's
> possible to specify on the command line exactly where
> password will be passed. The possible ways right now
> are through stdin, through any other fd, through an
> environment variable or directly on the command line.
That's good news.
--
http://www.guug.de/~roessler/
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
