RFC: JDK-8282648: Problems due to conflicting specification of Inflater::inflate(..) and InflaterInputStream::read(..)

[Alan Bateman]

On 28/03/2022 11:02, Volker Simonis wrote:
> :
> As I wrote before, the extra data written into the output buffer isn't
> sensitive because it can only originate from the history buffer (aka
> "sliding window"). Also, this data is already exposed today if the
> `Inflater` class is being used stand-alone, because in contrast to
> `InflaterInputStream::read(..)`, `Inflater::inflate(..)` doesn't
> guarantee to leave the content beyond the last read byte unaffected.
> Finally, the referenced zlib-chromium implementation with the
> mentioned behavior is the default zlib implementation in on Android
> and Chrome browsers.
If you are satisfied that flipping bits during an inflate operation 
cannot never lead to something bad happening then okay. I'ts important 
to ask about such as matters.

-Alan