This question relates to the following topic:
but here I ask it regarding a more sensitive security aspect.
Our users may upload images that contain protected content in the image metadata (e.g. EXIF, header information etc…) which don’t display in the image preview, content they are not supposed to share for confidentiality reasons. However, they may simply forget those metadata are in there and upload the image.
So contrary to the topic that I linked above, we do not want to make the image download more difficult (and only possible for tech savvy people), we want to make it impossible to get access to the metadata/EXIF data. The image itself, what is displayed in the post, is not what we need to protect (we don’t care if someone makes a screenshot or get it to full res).
So is there a mechanism in place with Discourse that facilitates the processing of images with some script/code (e.g. Python , C, C++) right after they are uploaded, and before the post shows up with it?
I do remember that the directory upload tree can be accessed for example to scan them for viruses, but that still is something happening as a concurrent process (which is still alright for us). Here we would want the processing of images to be blocking, to be sure that a swift user cannot have time to grab that image and its metadata before the process has completed.
Alternatively, if there have been an update since the topic linked above was made, making it absolutely impossible to download the image and, in particular, its metadata/EXIF, then that would solve the issue.