From: ludo@gnu.org (Ludovic Courtès)
To: ding@gnus.org
Subject: sieve-manage & starttls
Date: Sun, 21 Nov 2010 15:22:58 +0100 [thread overview]
Message-ID: <878w0m3ge5.fsf_-_@gnu.org> (raw)
In-Reply-To: <8762x6m7i0.fsf@gnu.org>
Hello!
ludo@gnu.org (Ludovic Courtès) writes:
> $ gnutls-cli --starttls -p 2000 imap.example.com
> Resolving 'imap.example.com'...
>
> - Simple Client Mode:
>
> "IMPLEMENTATION" "dovecot"
> "SASL" ""
> "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy"
> "STARTTLS"
> "RENAME"
> OK "mail server - Dovecot ready."
> STARTTLS
> OK "Begin TLS negotiation now."
> *** Starting TLS handshake
> - Ephemeral Diffie-Hellman parameters
> - Using prime: 1024 bits
> - Secret key: 1021 bits
> - Peer's public key: 1023 bits
> - Certificate type: X.509
> - Got a certificate list of 1 certificates.
> - Certificate[0] info:
> - subject `...’
> - The hostname in the certificate matches 'imap.example.com'.
> - Peer's certificate issuer is unknown
> - Peer's certificate is NOT trusted
> - Version: TLS1.0
> - Key Exchange: DHE-RSA
> - Cipher: AES-128-CBC
> - MAC: SHA1
> - Compression: NULL
> "IMPLEMENTATION" "dovecot"
> "SASL" "PLAIN"
> "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy"
> "RENAME"
> OK "TLS negotiation successful."
I’ve tried ‘sieve-manage’ from Gnus HEAD.
One problem illustrated by the example above is that capabilities must
be re-parsed after STARTTLS authentication. This is complicated by the
fact that ‘gnutls-cli’ emits TLS information upon successful handshake
(the lines that start with a hyphen above), which
‘sieve-manage-parse-capability-1’ should ignore.
I’ve tried to work on this without success so far, so I’d welcome help
or even patches. :-)
Thanks,
Ludo’.
prev parent reply other threads:[~2010-11-21 14:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 16:16 [PATCH] sieve-manage: use auth-source Julien Danjou
2010-10-05 17:18 ` Lars Magne Ingebrigtsen
2010-10-05 17:28 ` Ted Zlatanov
2010-10-08 15:40 ` Ted Zlatanov
2010-10-08 16:01 ` Julien Danjou
2010-10-13 14:39 ` Ludovic Courtès
2010-10-13 14:44 ` Julien Danjou
2010-10-13 15:34 ` Ludovic Courtès
2010-10-13 15:51 ` Julien Danjou
2010-10-13 18:26 ` Lars Magne Ingebrigtsen
2010-10-13 18:35 ` Julien Danjou
2010-10-13 18:52 ` Lars Magne Ingebrigtsen
2010-10-14 9:54 ` Julien Danjou
2010-10-14 18:58 ` Lars Magne Ingebrigtsen
2010-10-14 19:09 ` Julien Danjou
2010-10-14 19:11 ` Lars Magne Ingebrigtsen
2010-10-14 19:24 ` Julien Danjou
2010-10-14 19:29 ` Lars Magne Ingebrigtsen
2010-11-21 14:22 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878w0m3ge5.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).