From: Glenn Morris <rgm@gnu.org>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 11267@debbugs.gnu.org
Subject: bug#11267: 24.0.95; gnutls.c: [0] (Emacs) fatal error: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).
Date: Thu, 19 Apr 2012 12:19:33 -0400 [thread overview]
Message-ID: <jffwbzsnhm.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20367.61741.640831.184941@gargle.gargle.HOWL> (Roland Winkler's message of "Thu, 19 Apr 2012 06:04:13 -0500")
"Roland Winkler" wrote:
> - What are reasonable values for this variable such that a safe
> client-server handshake remains possible, if one needs to customize
> this variable? (Or the other way round: if a server wants to use a
> prime that is too small, it might really be the better solution to
> contact its sysadmin. Yet I couldn't tell when a prime falls below
> such a threshold.)
I also wonder how it can be safer to fall back to no encryption at all,
rather than using weak encryption (if that is indeed what is happening).
Maybe it's to prevent a false sense of security, or something.
next prev parent reply other threads:[~2012-04-19 16:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 8:52 bug#15057: 24.3.50; TLS error with reasonably high gnutls-min-prime-bits Tassilo Horn
2013-08-11 20:03 ` Lars Magne Ingebrigtsen
2013-10-07 22:27 ` Ted Zlatanov
2014-01-31 0:46 ` Lars Ingebrigtsen
2014-02-10 2:15 ` Ted Zlatanov
2012-04-17 21:14 ` bug#11267: 24.0.95; gnutls.c: [0] (Emacs) fatal error: The Diffie-Hellman prime sent by the server is not acceptable (not long enough) Roland Winkler
2012-04-18 16:48 ` Glenn Morris
2012-04-19 11:04 ` Roland Winkler
2012-04-19 16:19 ` Glenn Morris [this message]
2012-04-19 16:26 ` Lars Magne Ingebrigtsen
2012-04-19 16:31 ` Glenn Morris
2012-04-19 16:41 ` Roland Winkler
2012-04-24 12:45 ` Ted Zlatanov
2012-04-24 20:04 ` Roland Winkler
2012-05-13 19:04 ` Lars Magne Ingebrigtsen
2012-05-15 8:24 ` Ted Zlatanov
2012-05-15 15:16 ` Chong Yidong
[not found] ` <mailman.1129.1337070368.855.bug-gnu-emacs@gnu.org>
2012-05-18 11:38 ` n.mavrogiannopoulos
2014-02-10 2:39 ` Ted Zlatanov
2014-02-10 3:06 ` Roland Winkler
2014-02-10 8:28 ` Nikos Mavrogiannopoulos
2014-02-10 2:58 ` bug#15057: 24.3.50; TLS error with reasonably high gnutls-min-prime-bits Lars Ingebrigtsen
2014-02-10 10:52 ` bug#11267: bug#15057: 24.3.50; TLS error with reasonably high gnutls-min-prime-bits, bug#11267: 24.0.95; gnutls.c: [0] (Emacs) fatal error: The Diffie-Hellman prime sent by the server is not acceptable (not long enough) Ted Zlatanov
2014-02-11 5:09 ` Lars Ingebrigtsen
2014-02-11 10:35 ` Nikos Mavrogiannopoulos
2014-02-11 14:21 ` bug#16253: bug#11267: " Ted Zlatanov
2014-02-11 22:49 ` Roland Winkler
2014-02-11 23:54 ` Ted Zlatanov
2014-02-12 4:30 ` bug#15057: " Lars Ingebrigtsen
2014-02-12 17:11 ` Ted Zlatanov
2014-02-12 4:29 ` Lars Ingebrigtsen
2014-12-08 19:43 ` bug#15057: 24.3.50; TLS error with reasonably high gnutls-min-prime-bits 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=jffwbzsnhm.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=11267@debbugs.gnu.org \
--cc=winkler@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 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).