Gnus development mailing list
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: tls-program
Date: Sun, 19 Sep 2010 19:42:44 +0200	[thread overview]
Message-ID: <87k4mh1vfv.fsf@randomsample.de> (raw)
In-Reply-To: <m38w2xx3qs.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 19 Sep 2010 15:27:39 +0200")

Lars Magne Ingebrigtsen writes:
> Steinar Bang <sb@dod.no> writes:
>
>> So they are the typical case for someone with a private dovecot imap
>> server, running on a debian box somewhere.
>
> Yes, that's what I would have imagined.

gnutls-cli accepts self-signed certificates by default:

- The hostname in the certificate matches 'mydomain.foobar'.
- Peer's certificate issuer is unknown
- Peer's certificate is NOT trusted

but it continues anyway. I think it only balks when you explicitly
specify your trusted CAs through --x509cafile or something similar. If
you specify your trusted CAs, it seems you can set tls-checktrust to
'ask and get a similar behavior like Thunderbird's et al.

However, a hostname mismatch is not tolerated, and can only be
overridden with --insecure. This shouldn't be the default,
though. Openssl indeed always continues by default, but I think a
hostname mismatch should at least be warned about.

-David



  reply	other threads:[~2010-09-19 17:42 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             ` tls-program Steinar Bang
2010-09-19 13:27               ` tls-program Lars Magne Ingebrigtsen
2010-09-19 17:42                 ` David Engster [this message]
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=87k4mh1vfv.fsf@randomsample.de \
    --to=deng@randomsample.de \
    --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).