summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2017-07-18 00:37:03 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2017-07-18 00:37:32 -0700
commit1a62721f2d82f7a35a9fc84864f6df0ede2c05c5 (patch)
tree2315cbb781025bce0e48eedac7b0a66799ceb26f /lisp/emacs-lisp
parent0083123499cc29e301c197218d3809b225675e57 (diff)
downloademacs-1a62721f2d82f7a35a9fc84864f6df0ede2c05c5.tar.gz
emacs-1a62721f2d82f7a35a9fc84864f6df0ede2c05c5.tar.bz2
emacs-1a62721f2d82f7a35a9fc84864f6df0ede2c05c5.zip
Port gnutls.c to older (buggier?) GnuTLS
Problem reported for GnuTLS 3.2.1 by Glenn Morris in: http://lists.gnu.org/archive/html/emacs-devel/2017-07/msg00716.html http://lists.gnu.org/archive/html/emacs-devel/2017-07/msg00742.html Although I don't see how this bug can occur with vanilla GnuTLS 3.2.1, perhaps hydra was using a modified GnuTLS. * src/gnutls.c (Fgnutls_ciphers): Don't assume GNUTLS_CIPHER_NULL is at the end of the list returned by gnutls_cipher_list, or that the earlier ciphers all have non-null names.
Diffstat (limited to 'lisp/emacs-lisp')
0 files changed, 0 insertions, 0 deletions