Does anyone know if JPEG XL encoders can be prone to the infamous JBIG2 "Pattern Matching & Substitution" region-reuse issue, that so badly affected Xerox copiers?

https://www.dkriesel.com/en/blog/2013/0802_xerox-workcentres_are_switching_written_numbers_when_scanning

#JPEG #JPEGXL #JBIG2 #Xerox

Des formats d'image

#images #pictures #graphisme #jbig2 #GIF #JPEG #PNG #SVG #format #webp #heic #hevc #avi #eps #pdf #svg

https://lsdm.live/modules/news/article.php?storyid=4203

Are there any easy-to-use #JBIG2 tools for #Linux?

Gimp doesn't seem to support it (yet?), and I just can't wrap my head around how to use jbig2enc -- it spits out some data to STDOUT that 'file' can't identify.
I just find the concept of lossy bilevel images compression fascinating, and I'd love to play with it to see how badly it would butcher something like a Floyd-Steinberg dithered image (and how much compression it'd actually accomplish)

Working through hitches with the last document:
- font in last tweet wasn't getting used (had to tweak it in FontForge)
- bits of text underlay visible (optimization fixed it)
- #jbig2 encoder used by #ocrmypdf optimization scrambled glyphs (disabled; I can't trust it now!)

#xp

#InfoSec #ProjectZero
> A deep dive into an #NSO zero-click #iMessage exploit: #RemoteCodeExecution
> #JBIG2 doesn't have scripting capabilities, but when combined with a vulnerability, it does have the ability to emulate circuits of arbitrary logic gates operating on arbitrary memory. So why not just use that to build your own computer architecture and script that!? That's exactly what this #exploit does.
https://googleprojectzero.blogspot.com/2021/12/a-deep-dive-into-nso-zero-click.html