From: Moritz Ulrich <moritz@tarn-vedra.de>
To: 13877@debbugs.gnu.org
Subject: bug#13877: 24.3; gnutls.el: Enable Certificate Checks
Date: Tue, 05 Mar 2013 11:40:09 +0100 [thread overview]
Message-ID: <m21ubuuo3a.fsf@tarn-vedra.de> (raw)
Currently, gnutls.el doesn't check certificate signatures when used via
`open-network-stream' with :type 'tls or `open-gnutls-stream'.
This is caused by the following code from `open-gnutls-stream'
(gnutls.el:110):
--8<---------------cut here---------------start------------->8---
(gnutls-negotiate :process (open-network-stream name buffer host service)
:type 'gnutls-x509pki
:hostname host)
--8<---------------cut here---------------end--------------->8---
There is NO way to set :verify-host, :verify-flags, etc. for this call
to `gnutls-negotiate' when using gnutls via high-level functions like
`open-network-stream'.
I consider this a bug, as Emacs won't check any certificates and
therefore allow man in the middle attacks without even documenting this.
It should at least be possible to pass :verify-* from
`open-network-stream' down to `gnutls-negotiate'. That would be a simple
yet effective solution.
In GNU Emacs 24.3.1 (x86_64-apple-darwin11.4.2, NS apple-appkit-1138.51)
of 2013-03-05 on Moritzs-MacBook-Air
Windowing system distributor `Apple', version 10.3.1138
Configured using:
`configure '--prefix=/usr/local/Cellar/emacs/24.3-rc1' '--without-dbus'
'--enable-locallisppath=/usr/local/share/emacs/site-lisp'
'--infodir=/usr/local/Cellar/emacs/24.3-rc1/share/info/emacs'
'--with-ns' '--disable-ns-self-contained' '--with-gnutls' '--with-jpeg'
'--with-xml2' '--with-imagemagick' 'CC=cc''
<#secure method=pgpmime mode=sign>
--
Moritz Ulrich
next reply other threads:[~2013-03-05 10:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 10:40 Moritz Ulrich [this message]
2013-03-05 16:51 ` bug#13877: 24.3; gnutls.el: Enable Certificate Checks Glenn Morris
2013-03-14 12:19 ` bug#13374: " Ted Zlatanov
2013-03-27 13:20 ` Ted Zlatanov
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=m21ubuuo3a.fsf@tarn-vedra.de \
--to=moritz@tarn-vedra.de \
--cc=13877@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.