Treat metadata removal as one upload-security check, not proof that an image contains only image data.
Removing EXIF GPS protects one privacy boundary. It does not prove that an uploaded JPEG contains only a JPEG.
A useful hostile fixture is a valid image followed by bytes for another format. Many decoders stop at JPEG’s end marker and display the picture successfully, while downstream scanners, content sniffers, or accidental downloads may interpret the trailing payload differently.
Build a fixture set rather than trusting extensions:
clean.jpg valid JPEG
exif-gps.jpg valid JPEG with location
Intercept the exact bytes uploaded after rotation, thumbnailing, background retry, and app restart.
Test the still image, paired video, temporary files, and retry queue as one privacy boundary.
A photo can disclose more than its visible pixels. Depending on the device and editing workflow, a...
Client-side media preflight can improve an upload experience, but it can also crash the page before...
Every developer has shipped an image that was too heavy, wrongly sized, or worse: one that still had...
TL;DR: The idea is to use a set of ordinary JPEG images as a distributed medium for an encrypted...
