Last modified: 2012-03-27 19:15:58 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T37514, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 35514 - [MW] EXIF data needs to be possible to remove automatically or optionally
[MW] EXIF data needs to be possible to remove automatically or optionally
Status: RESOLVED DUPLICATE of bug 20326
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
1.18.x
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-27 06:00 UTC by badon
Modified: 2012-03-27 19:15 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description badon 2012-03-27 06:00:26 UTC
EXIF data can be used to discover the owner of valuables photographed and uploaded to a MediaWiki site. From there, kidnappings and other tragedies are a serious risk that cannot be ignored. Most people believe kidnappings are rare, but in fact, they are just not reported for the obvious reason that the anxious parents want their kids back, and they will not report the kidnapping if that puts their children at risk (it does). Kidnappings are common enough that the insurance industry is involved in paying ransoms:

https://www.google.com/search?q=kidnap+insurance

Kidnappings are the worst case scenario, but anything that attracts criminal attention should be carefully evaluated and dealt with like any other security risk, and not dismissed as unlikely or "not my problem" - just ask Kevin Mitnick, who exploited "unimportant" underlings to reach larger criminal objectives, in much the same way a kidnapper exploits children to reach the parents, and the parents' bank.

GPS data is the most potent risk in EXIF data, but the other data may provide enough information to cause the identification of a criminal target. The ability remove GPS data, and/or most other EXIF data, is critical for protecting both the ignorant and the innocent, who can be indirectly harmed by EXIF data that they may not even be aware of.

Simply hiding the EXIF metadata display is worse than displaying it, because not displaying it still leaves the ignorant unaware that it exists. That is one of the well-known pitfalls of security through obscurity. 

So, there needs to be at least something like a checkbox that an uploader can use to indicate they want MediaWiki to remove EXIF data. The ability for a wiki to be configured to always automatically remove EXIF data is also required to achieve "fail safe", in some circumstances. 

The stakes are potentially very high, so until this is implemented, the bare minimum would be some sort of link to a page like this one, with information on how to remove the EXIF data:

http://commons.wikimedia.org/wiki/Commons:EXIF

Of course, informing the uploader of the risks would also be helpful in dealing with the ignorance part of the problem, which that page currently does not have. There has been media attention to the problems that EXIF data can cause for people:

http://www.nytimes.com/2010/08/12/technology/personaltech/12basics.html

That causes people to be hesitant in uploading their images. Addressing this issue can eliminate some of the objections potential contributers might have that prevents them from sharing their images.
Comment 1 Bawolff (Brian Wolff) 2012-03-27 13:14:51 UTC
Dupe of bug 20326 (Although you  give a much more in depth explanation for the why we need to do this then the other bug does)

*** This bug has been marked as a duplicate of bug 20326 ***
Comment 2 badon 2012-03-27 19:15:58 UTC
I thought I had thoroughly searched for dupes, but the main keyword I used was "EXIF", so that previous report didn't show up for me. Thanks for finding it for me.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links