From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: tls-program
Date: Sun, 19 Sep 2010 15:21:19 +0200 [thread overview]
Message-ID: <871v8pq374.fsf@dod.no> (raw)
In-Reply-To: <m3iq21zzqy.fsf@quimbies.gnus.org>
>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Well, if having invalid certificates is really common on IMAP servers,
> then annoying them with this would be... annoying.
They aren't neccessarily invalid. In many cases they are self signed,
and can't be verified because they aren't signed by a CA in the client's
certificate store.
So they are the typical case for someone with a private dovecot imap
server, running on a debian box somewhere.
next prev parent reply other threads:[~2010-09-19 13:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-18 22:29 tls-program Lars Magne Ingebrigtsen
2010-09-18 22:44 ` tls-program Ludovic Courtès
2010-09-18 22:46 ` tls-program Sebastian Krause
2010-09-18 22:51 ` tls-program Sebastian Krause
2010-09-18 22:58 ` tls-program Lars Magne Ingebrigtsen
2010-09-18 23:05 ` tls-program Sebastian Krause
2010-09-18 23:47 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 4:20 ` tls-program Daniel Pittman
2010-09-19 12:25 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 13:21 ` Steinar Bang [this message]
2010-09-19 13:27 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 17:42 ` tls-program David Engster
2010-09-19 17:47 ` tls-program Lars Magne Ingebrigtsen
2010-09-20 14:53 ` tls-program Ted Zlatanov
2010-09-21 16:11 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 15:48 ` tls-program Frank Schmitt
2010-09-19 15:58 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 8:48 ` tls-program Tibor Simko
2010-09-19 12:28 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 12:29 ` tls-program Lars Magne Ingebrigtsen
2010-09-19 19:17 ` tls-program James Cloos
2010-09-19 19:15 ` tls-program James Cloos
2010-09-19 19:21 ` tls-program Lars Magne Ingebrigtsen
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=871v8pq374.fsf@dod.no \
--to=sb@dod.no \
--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).