From 29f404ba5cc9ea9335ee3c698ff52f151887c2e7 Mon Sep 17 00:00:00 2001 From: Jeffrey Walton Date: Sat, 19 Aug 2017 09:09:21 -0400 Subject: Update comments (Issue 414) After more investigation it appears the issue was either Undefined Behavior or a Strict Aliasing violation in GCC; and it was in the test program and not the library. We're not sure which at the moment, but we were able to identify the problematic code. See the comments with Issue 414 (https://github.com/weidai11/cryptopp/issues/414) --- zinflate.cpp | 2 -- 1 file changed, 2 deletions(-) (limited to 'zinflate.cpp') diff --git a/zinflate.cpp b/zinflate.cpp index 41690ef9..7e9de15b 100644 --- a/zinflate.cpp +++ b/zinflate.cpp @@ -556,7 +556,6 @@ bool Inflator::DecodeBody() break; } case DISTANCE_BITS: - // TODO: this surfaced during fuzzing. What do we do??? CRYPTOPP_ASSERT(m_distance < COUNTOF(distanceExtraBits)); if (m_distance >= COUNTOF(distanceExtraBits)) throw BadDistanceErr(); @@ -566,7 +565,6 @@ bool Inflator::DecodeBody() m_nextDecode = DISTANCE_BITS; break; } - // TODO: this surfaced during fuzzing. What do we do??? CRYPTOPP_ASSERT(m_distance < COUNTOF(distanceStarts)); if (m_distance >= COUNTOF(distanceStarts)) throw BadDistanceErr(); -- cgit v1.2.1