Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Built-in TLS vs. nnimap security
Date: Thu, 18 Aug 2011 02:30:05 +0200	[thread overview]
Message-ID: <m3mxf7tvci.fsf@stories.gnus.org> (raw)
In-Reply-To: <87pqkgf7pw.fsf@silenus.orebokech.com>

Romain Francoise <romain@orebokech.com> writes:

> Is it a feature or a bug that when the built-in GnuTLS support is loaded
> in Emacs, nnimap happily connects to my test imaps server even though the
> certificate is self-signed and doesn't match the hostname?

It's a ... er ... missing feature.  :-)

> Actually, shouldn't `open-gnutls-stream' do these checks by default
> anyway? It's a new implementation, it doesn't have to follow the (poor)
> historical defaults set by tls.el.

Yes, it's meant to do that, but nobody has actually implemented the
needed callbacks, I seem to remember?  Or did Ted do that, and I missed
it?  I was going to do the `open-network-stream' querying thing after
the required callbacks were in place.  The last thing I seem to vaguely
recall was Ted saying something about different verification callback
structures in different versions of the gnutls libraries, which made
things awkward.

But I may be misremembering.  Anybody?  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/




  reply	other threads:[~2011-08-18  0:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 11:44 Romain Francoise
2011-08-18  0:30 ` Lars Magne Ingebrigtsen [this message]
2011-09-29  9:07   ` Ted Zlatanov
2011-10-06 21:23     ` 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=m3mxf7tvci.fsf@stories.gnus.org \
    --to=larsi@gnus.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).