From: Ted Zlatanov <tzz@lifelogs.com>
To: sb@dod.no
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, 16784@debbugs.gnu.org
Subject: bug#16784: 24.3; Problems opening NNTP connection: failing starttls because of a non-verified certificate
Date: Thu, 20 Mar 2014 10:48:25 -0400 [thread overview]
Message-ID: <874n2t3ozq.fsf@lifelogs.com> (raw)
In-Reply-To: <87ob24ctq3.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 18 Feb 2014 10:43:00 -0500")
On Tue, 18 Feb 2014 10:43:00 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Mon, 17 Feb 2014 18:50:32 +0100 sb@dod.no wrote:
s> Entering news.gmane.no nntp groups in gnus fails on Windows, because it
s> tries to upgrade the connection using STARTTLS and fails because the
s> news.gmane.org certificate is self signed.
SB> I would like one of the following solutions:
SB> 1. The possibility to switch off the attempted upgrade to STARTTLS for
SB> NNTP connections
I think Lars has to give an opinion here.
SB> 2. The possibility to tell GNU-TLS not to be so stringent about
SB> certificate verification
The latest Emacs trunk has this:
(defcustom gnutls-verify-error nil
"If non-nil, this should be a list of checks per hostname regex or t."
:group 'gnutls
:version "24.4"
:type '(choice
(const t)
(repeat :tag "List of hostname regexps with flags for each"
(list
(choice :tag "Hostname"
(const ".*" :tag "Any hostname")
regexp)
(set (const :trustfiles)
(const :hostname))))))
So basically customize that variable and add :trustfiles and :hostname
for the respective verifications, or nil to disable them.
Also note that internally, we use some default flags for
`gnutls-negotiate'. From the docstring:
VERIFY-FLAGS is a numeric OR of verification flags only for
`gnutls-x509pki' connections. See GnuTLS' x509.h for details;
here's a recent version of the list.
GNUTLS_VERIFY_DISABLE_CA_SIGN = 1,
GNUTLS_VERIFY_ALLOW_X509_V1_CA_CRT = 2,
GNUTLS_VERIFY_DO_NOT_ALLOW_SAME = 4,
GNUTLS_VERIFY_ALLOW_ANY_X509_V1_CA_CRT = 8,
GNUTLS_VERIFY_ALLOW_SIGN_RSA_MD2 = 16,
GNUTLS_VERIFY_ALLOW_SIGN_RSA_MD5 = 32,
GNUTLS_VERIFY_DISABLE_TIME_CHECKS = 64,
GNUTLS_VERIFY_DISABLE_TRUSTED_TIME_CHECKS = 128,
GNUTLS_VERIFY_DO_NOT_ALLOW_X509_V1_CA_CRT = 256
It must be omitted, a number, or nil; if omitted or nil it
defaults to GNUTLS_VERIFY_ALLOW_X509_V1_CA_CRT.
This is the current default, except as modified by the GnuTLS priority
string. I would expect callers such as Gnus to modify this, but not
normal users.
Ted
next prev parent reply other threads:[~2014-03-20 14:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 17:50 bug#16784: 24.3; Problems opening NNTP connection: failing starttls because of a non-verified certificate sb
2014-02-18 15:43 ` Ted Zlatanov
2014-03-20 14:48 ` Ted Zlatanov [this message]
2014-03-20 14:58 ` Lars Magne Ingebrigtsen
2014-03-21 10:23 ` Ted Zlatanov
2014-03-21 10:33 ` Steinar Bang
2014-03-24 12:14 ` Lars Magne Ingebrigtsen
2014-12-08 20:07 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874n2t3ozq.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=16784@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=sb@dod.no \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).