From: Robert Pluim <rpluim@gmail.com>
To: Amin Bandali <bandali@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Network Security Manager warns safe renegotiation is not supported
Date: Thu, 05 Sep 2019 08:51:23 +0200 [thread overview]
Message-ID: <m2sgpbme1g.fsf@gmail.com> (raw)
In-Reply-To: 875zmcdlc9.fsf@fencepost.gnu.org
>>>>> On Sun, 01 Sep 2019 12:37:10 -0400, Amin Bandali <bandali@gnu.org> said:
Amin> I’m no security expert, but I don’t think that’s a good idea. Setting
Amin> `gnutls-algorithm-priority' to that value basically tells GnuTLS to skip
Amin> TLS1.3 altogether, which is the latest version of the TLS protocol.
Amin> The issue seems to be that nsm.el checks for renegotiation_info[1] for
Amin> TLS1.3 connections as well; but if I understand correctly, renegotiation
Amin> was removed from TLS1.3, according to [2] and [3]. I *think* the proper
Amin> way to fix this would be have nsm *not* check for renegotiation-info-ext
Amin> for TlS1.3 connections. Please don’t take my word for this as, again,
Amin> I’m no security/GnuTLS expert. Hopefully others with more knowledge can
Amin> chime in to clarify.
Correct. Fixed in emacs-master.
Robert
next prev parent reply other threads:[~2019-09-05 6:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 23:23 Network Security Manager warns safe renegotiation is not supported Yuji Nakao
2019-09-01 15:38 ` Jude DaShiell
2019-09-01 16:37 ` Amin Bandali
2019-09-05 6:51 ` Robert Pluim [this message]
2019-09-05 7:53 ` Herbert J. Skuhra
2019-09-05 9:38 ` Robert Pluim
2019-09-05 10:02 ` Herbert J. Skuhra
2019-09-05 11:22 ` Robert Pluim
2019-09-05 11:51 ` Robert Pluim
[not found] ` <mailman.418.1567684317.2075.help-gnu-emacs@gnu.org>
2019-09-05 12:51 ` Lars Magne Ingebrigtsen
2019-09-05 13:44 ` Robert Pluim
[not found] ` <mailman.423.1567691091.2075.help-gnu-emacs@gnu.org>
2019-09-05 13:51 ` Lars Magne Ingebrigtsen
2019-09-05 14:02 ` Robert Pluim
2019-09-05 19:09 ` Herbert J. Skuhra
2019-09-05 12:03 ` Herbert J. Skuhra
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=m2sgpbme1g.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=bandali@gnu.org \
--cc=help-gnu-emacs@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.
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).