Full Disclosure mailing list archives

Re: avoid jpeg overflow problems using on the fly conversion?

From: Valdis.Kletnieks () vt edu
Date: Fri, 17 Sep 2004 12:04:26 -0400

On Fri, 17 Sep 2004 23:03:10 +1200, Nick FitzGerald said:

And, your suggestion does not say what to do with "bad" JPEGs -- it 
seems you assume the JPG to PNG convertor will necessarily and 
"correctly" deal with such invalid input.  Do we really know that is a 
valid assumption?


There's also another sticky issue - it seems at least one release of AOL's
"net accelerator" basically consisted of code that downgraded all the .JPG
to a higher-compression (therefore more lossy) format.  Some questioned
what this meant for places like corbis.com, who make money selling *high*
quality images.  Applying type conversions like this is always fraught with
unintended consequences... :)

Bonus points for figuring out how to make the filtering work if the
front-end points at an https: :)

Attachment: _bin
Description:

Current thread:

re jpeg vuln mike gringo (Sep 16)
- avoid jpeg overflow problems using on the fly conversion? mettlers (Sep 17)
  - Re: avoid jpeg overflow problems using on the fly conversion? Nick FitzGerald (Sep 17)
    - Re: avoid jpeg overflow problems using on the fly conversion? Valdis . Kletnieks (Sep 17)
    - Re: avoid jpeg overflow problems using on the fly conversion? Sascha Mettler (Sep 18)
  - Re: avoid jpeg overflow problems using on the fly conversion? William Warren (Sep 17)