Age | Commit message (Collapse) | Author | |
---|---|---|---|
2006-05-18 | Avoid safe_free() usage and add security checks | Rocco Rutte | |
Add checks to check_sec.sh for memory functions. These include a check for use of safe_free() instead of FREE() and a check whether FREE(&...) is used. For the former, __SAFE_FREE_CHECKED__ is to be used, for the latter __FREE_CHECKED__ to avoid messages from check_sec.sh | |||
2004-10-30 | safe_strcat, safe_strncat. Thanks to Ulf H. for noting the wrong | Thomas Roessler | |
use of strncat in part of the mutt code base. | |||
2002-05-01 | Give all the warnings at once. | Thomas Roessler | |
2001-06-07 | Don't check in intl/ | Thomas Roessler | |
2001-01-08 | Let check_sec.sh check for use of the unsafe malloc, realloc, free, | Thomas Roessler | |
and strdup routines. While we are on it, plug some memory leaks and make some code understandable. | |||
2001-01-08 | Fix and/or check more fishy code. | Thomas Roessler | |
2001-01-08 | Going through possible security problems with a fine comb. If you | Thomas Roessler | |
want to help, check out the current source, and run check_sec.sh. | |||
2001-01-08 | Some automated security checks concerning fopen() calls. | Thomas Roessler | |