Re: [PATCH 0/2] Two small fixes to gzip

Hey, On Sat, May 18, 2024 at 02:52:20PM +1000, Daniel Axtens wrote: > Hi Daniel, > > > Reviewed-by: Daniel Kiper for both patches... > > Thank you! > > > I assume I can add your SOB on your behalf... > > Oh! Yes! Sorry, 2 years of closed source development have apparently caused > me to lose my

Re: [PATCH 0/2] Two small fixes to gzip

Hi Daniel, > Reviewed-by: Daniel Kiper for both patches... Thank you! > I assume I can add your SOB on your behalf... Oh! Yes! Sorry, 2 years of closed source development have apparently caused me to lose my 'git commit -s' habits! The sign-off for both patches is: Signed-off-by: Daniel

Re: [PATCH 0/2] Two small fixes to gzip

On Mon, May 13, 2024 at 12:32:07AM +1000, Daniel Axtens wrote: > I've been fuzzing gzip a bit. So far nothing super exciting, but it's helpful > to add some code to bail early on EOF (patch 1) and to avoid some > uninitialised > data warnings from valgrind (patch 2). I'm not aware of any security

[PATCH 0/2] Two small fixes to gzip

I've been fuzzing gzip a bit. So far nothing super exciting, but it's helpful to add some code to bail early on EOF (patch 1) and to avoid some uninitialised data warnings from valgrind (patch 2). I'm not aware of any security implications of either change, and the gzip compression test still