I didn't subscribe [EMAIL PROTECTED],
please append 'CC: [EMAIL PROTECTED]'.
I read next URL.
http://www.mail-archive.com/[email protected]/msg02877.html
I wrote:
> Hi.
> I implemented STARTTLS documented in RFC2487.
> I can't use STARTTLS with s_client.
> I added a new command 'starttls',
> which says 'STARTTLS' after a connection.
> The code of starttls.c consist almost of s_client.c.
Lutz wrote:
> thank you very much for your detailed error description.
>
> What kind of software do you use for testing?
> To test your server side, use Netscape >= 4.5 with SSL/TLS enabled.
> Once you have your server running, re-test your client.
> You may consider using one of the available OpenSource RFC2487
> implementations.
> You can start with mine at
> http://www.aet.tu-cottbus.de/personen/jaenicke/postfix_tls
> and by having a look into my references you can check the others.
I use qmail-1.0.3 + tls.patch(*) and some MUA,
which include Netscape >= 4.5.
They work correctly, and this mail will be sent
with DES-CBC3-SHA encrypted SMTP(RFC2487).
(*) http://www.esat.kuleuven.ac.be/~vermeule/qmail/tls.patch
I regret that I cannot explain myself.
I'm a developer of a MUA(see my User-Agent) with emacs lisp,
and I need a backend such as s_client for SASL,
S_client cannot, however, use for SASL.
A connection with SASL needs to say 'STARTTLS' before a certification of TLS,
but s_client immediately starts a certification after a connection of TCP.
What is the best way for SASL?
I sent a patch(openssl-0.9.4-starttls.patch), which the starttls command
implements a SASL client with.
<[EMAIL PROTECTED]>
For example.
% openssl starttls -host localhost -port 25
cf.
% telnet localhost 25
I would like to ask the opinion of the participants.
--
Kenichi Okada
mailto:[EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
