diff options
| author | Mark Adler <madler@alumni.caltech.edu> | 2011-09-09 23:22:10 -0700 |
|---|---|---|
| committer | Mark Adler <madler@alumni.caltech.edu> | 2011-09-09 23:22:10 -0700 |
| commit | 8e34b3a8024c028dd9fd21d70525fc6d215efde5 (patch) | |
| tree | 896a32f54abdf42ae3c1bb3c5d5627668b481ce4 /FAQ | |
| parent | 13a294f044ef0a89b2dcbfbb5d4d4c792673348e (diff) | |
| download | zlib-8e34b3a8024c028dd9fd21d70525fc6d215efde5.tar.gz | |
zlib 1.2.0.2v1.2.0.2
Diffstat (limited to 'FAQ')
| -rw-r--r-- | FAQ | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -228,7 +228,8 @@ The lastest zlib FAQ is at http://www.gzip.org/zlib/zlib_faq.html hand, if zlib is compiled to use snprintf() or vsnprintf(), which should normally be the case, then there is no vulnerability. The ./configure script will display warnings if an insecure variation of sprintf() will - be used by gzprintf(). + be used by gzprintf(). Also the zlibCompileFlags() functions will return + information on what variant of sprintf() is used by gzprintf(). If you don't have snprintf() or vsnprintf() and would like one, you can find a portable implementation here: |