1 files changed, 2 insertions, 1 deletions
diff --git a/FAQ b/FAQ
index 2a8247c..b439bd9 100644
--- a/FAQ
+++ b/FAQ
@@ -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:

diff --git a/FAQ b/FAQ index 2a8247c..b439bd9 100644 --- a/FAQ +++ b/FAQ
@@ -228,7 +228,8 @@ The lastest zlib FAQ is at http://www.gzip.org/zlib/zlib_faq.html
228	hand, if zlib is compiled to use snprintf() or vsnprintf(), which should	228	hand, if zlib is compiled to use snprintf() or vsnprintf(), which should
229	normally be the case, then there is no vulnerability. The ./configure	229	normally be the case, then there is no vulnerability. The ./configure
230	script will display warnings if an insecure variation of sprintf() will	230	script will display warnings if an insecure variation of sprintf() will
231	be used by gzprintf().	231	be used by gzprintf(). Also the zlibCompileFlags() functions will return
		232	information on what variant of sprintf() is used by gzprintf().
232		233
233	If you don't have snprintf() or vsnprintf() and would like one, you can	234	If you don't have snprintf() or vsnprintf() and would like one, you can
234	find a portable implementation here:	235	find a portable implementation here: