Mercurial > hg > xemacs-beta
view etc/toolbar/info-def-up.xpm @ 5892:053ef01b71a8
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 | 7910031dd78a |
| children |
line wrap: on
line source
/* XPM */ /* This file is part of XEmacs. XEmacs is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. XEmacs is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with XEmacs. If not, see <http://www.gnu.org/licenses/>. */ static char * info[] = { "28 28 2 1", "X c Gray75 s backgroundToolBarColor", "o c black s foregroundToolBarColor", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXoooooooXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXXXoXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXooooooXXXXXXXXXXXX", "XXXXXXXXXoooooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXXoooooXXXXXXXXXXXX", "XXXXXXXXXXoooooooXXXXXXXXXXX", "XXXXXXXXXoooooooooXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX", "XXXXXXXXXXXXXXXXXXXXXXXXXXXX"};