From: Glenn Morris <rgm@gnu.org>
To: 27708@debbugs.gnu.org
Cc: eggert@cs.ucla.edu
Subject: bug#27708: [PROPOSED] Simplify configuration of HAVE_GNUTLS3 etc.
Date: Thu, 03 Aug 2017 17:32:59 -0400 [thread overview]
Message-ID: <8th8xonxpw.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <874lto9zer.fsf@lifelogs.com> (Ted Zlatanov's message of "Thu, 03 Aug 2017 16:20:12 -0400")
Ted Zlatanov wrote:
> I think that this means that one of MD5, SHA1, SHA224, SHA256, SHA384,
> or SHA512 (the `secure-hash-algorithms' members currently) are not in
> that version of GnuTLS.
>
> That is not really necessary. I was overzealous writing the tests; we
> can just test the `secure-hash-algorithms' that are in GnuTLS.
Before a8a81df:
(mapcar 'car (gnutls-ciphers))
->
(RC2-40 ARCFOUR-40 DES-CBC 3DES-CBC CAMELLIA-256-GCM CAMELLIA-128-GCM
CAMELLIA-128-CBC CAMELLIA-192-CBC CAMELLIA-256-CBC SALSA20-256
ESTREAM-SALSA20-256 ARCFOUR-128 AES-256-GCM AES-128-GCM AES-128-CBC
AES-192-CBC AES-256-CBC)
After a8a81df:
(gnutls-ciphers) -> nil
which seems a pretty drastic change to me.
Again, this is with:
#define GNUTLS_VERSION "3.3.24"
#define GNUTLS_VERSION_NUMBER 0x030318
next prev parent reply other threads:[~2017-08-03 21:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-15 16:14 bug#27708: [PROPOSED] Simplify configuration of HAVE_GNUTLS3 etc Paul Eggert
2017-07-15 16:33 ` Eli Zaretskii
2017-07-15 19:11 ` Ted Zlatanov
2017-07-15 19:22 ` Eli Zaretskii
2017-07-16 0:31 ` Paul Eggert
2017-07-16 2:36 ` Eli Zaretskii
2017-07-16 15:18 ` Paul Eggert
2017-07-16 16:08 ` Eli Zaretskii
2017-07-17 15:03 ` Ted Zlatanov
2017-07-26 21:04 ` Ted Zlatanov
2017-07-26 23:23 ` Paul Eggert
2017-07-27 21:11 ` Ted Zlatanov
2017-08-03 2:50 ` Paul Eggert
2017-08-03 16:06 ` Glenn Morris
2017-08-03 20:20 ` Ted Zlatanov
2017-08-03 20:31 ` Paul Eggert
2017-08-03 20:45 ` Ted Zlatanov
2017-08-03 21:32 ` Glenn Morris [this message]
2017-08-04 1:41 ` Paul Eggert
2017-08-04 13:32 ` 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=8th8xonxpw.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=27708@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.