From: Robert Pluim <rpluim@gmail.com>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: emacs-26 3302b7c: Mention the NSM in the gnutls variable doc strings
Date: Mon, 09 Jul 2018 13:49:20 +0200 [thread overview]
Message-ID: <87va9omxxb.fsf@gmail.com> (raw)
In-Reply-To: <20180708135931.BCDF7205D8@vcs0.savannah.gnu.org> (Lars Ingebrigtsen's message of "Sun, 8 Jul 2018 09:59:31 -0400 (EDT)")
larsi@gnus.org (Lars Ingebrigtsen) writes:
> @@ -111,7 +123,14 @@ number with fewer than this number of bits, the handshake is
> rejected. \(The smaller the prime number, the less secure the
> key exchange is against man-in-the-middle attacks.)
>
> -A value of nil says to use the default GnuTLS value."
> +A value of nil says to use the default GnuTLS value.
> +
> +The default value of this variable is such that virtually any
> +connection can be established, whether this connection can be
> +considered cryptographically \"safe\" or not. However, Emacs
> +network security is handled at a higher level via
> +`open-network-stream' and the Network Security Manager. See Info
> +node `(emacs) Network Security'."
> :type '(choice (const :tag "Use default value" nil)
> (integer :tag "Number of bits" 512))
> :group 'gnutls)
So gnutls-min-prime-bits is still 256, but the NSM on its default
'medium' level will complain if it negotiates < 1024? Would it not
make more sense to set it to nil then? People who really need it at
256 can set it to that (and it should really be settable per-host, but
thatʼs a different issue).
Regards
Robert
next parent reply other threads:[~2018-07-09 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180708135930.31863.22883@vcs0.savannah.gnu.org>
[not found] ` <20180708135931.BCDF7205D8@vcs0.savannah.gnu.org>
2018-07-09 11:49 ` Robert Pluim [this message]
2018-07-09 11:53 ` emacs-26 3302b7c: Mention the NSM in the gnutls variable doc strings Lars Ingebrigtsen
2018-07-09 13:27 ` Robert Pluim
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=87va9omxxb.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@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.
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.