comparison tests/ChangeLog @ 5891:a0e751d6c3ad

Import the #'clear-string API from GNU, use it in tls.c src/ChangeLog addition: 2015-04-18 Aidan Kehoe <kehoea@parhasard.net> * sequence.c (Fclear_string): New, API from GNU. Zero a string's contents, making sure the text is not kept around even when the string's data is reallocated because of a changed character length. * sequence.c (syms_of_sequence): Make it available to Lisp. * lisp.h: Make it available to C code. * tls.c (nss_pk11_password): Use it. * tls.c (gnutls_pk11_password): Use it. * tls.c (openssl_password): Use it. tests/ChangeLog addition: 2015-04-18 Aidan Kehoe <kehoea@parhasard.net> * automated/lisp-tests.el: Test #'clear-string, just added. Unfortunately there's no way to be certain from Lisp that the old password data has been erased after realloc; it may be worth adding a test to tests.c, but *we'll be reading memory we shouldn't be*, so that gives me pause.
author Aidan Kehoe <kehoea@parhasard.net>
date Sat, 18 Apr 2015 23:00:14 +0100
parents c96000075e49
children d3d073aceaea
comparison
equal deleted inserted replaced
5888:a85efdabe237 5891:a0e751d6c3ad
1 2015-04-18 Aidan Kehoe <kehoea@parhasard.net>
2
3 * automated/lisp-tests.el:
4 Test #'clear-string, just added. Unfortunately there's no way to
5 be certain from Lisp that the old password data has been erased
6 after realloc; it may be worth adding a test to tests.c, but
7 *we'll be reading memory we shouldn't be*, so that gives me pause.
8
1 2015-04-08 Aidan Kehoe <kehoea@parhasard.net> 9 2015-04-08 Aidan Kehoe <kehoea@parhasard.net>
2 10
3 * automated/lisp-tests.el: 11 * automated/lisp-tests.el:
4 Add a couple of tests for #'parse-integer to check for a bug just 12 Add a couple of tests for #'parse-integer to check for a bug just
5 fixed. 13 fixed.