Mercurial > cgi-bin > hgweb.cgi > JpegWasher

comparison Readme.html @ 17:0528030187e9

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
More Readme updates.
author David Barts <n5jrn@me.com>
date Sat, 11 Apr 2020 13:38:26 -0700
parents 304492a6b72b
children 0161374f7a60
comparison
equal deleted inserted replaced
16:304492a6b72b 17:0528030187e9
73 <p>If you disagree with ExifWasher’s decisions, you can check or uncheck the 73 <p>If you disagree with ExifWasher’s decisions, you can check or uncheck the
74 boxes next to the metadata in question. When you are satisfied with the 74 boxes next to the metadata in question. When you are satisfied with the
75 choice of metadata to be scrubbed, click “Wash” and all offending metadata 75 choice of metadata to be scrubbed, click “Wash” and all offending metadata
76 will be removed. A dialog will pop up showing the metadata remaining in 76 will be removed. A dialog will pop up showing the metadata remaining in
77 the new, washed file.</p> 77 the new, washed file.</p>
78 <h3>Important: Run ExifWasher Last!</h3>
79 <p>Most image-editing tools insert telltale bits of metadata into the output
80 they create. Thus, only way you can create a file with the minimum amount
81 of metadata in it is to run ExifWasher as the final step in your image
82 preparation.</p>
78 <h2>Output Files</h2> 83 <h2>Output Files</h2>
79 <p>ExifWasher never modifies an existing image file. Instead, it creates a 84 <p>ExifWasher never modifies an existing image file. Instead, it creates a
80 new file of the same type but with “_washed” appended to its name. For 85 new file of the same type but with “_washed” appended to its name. For
81 example, processing <code>foo.jpg</code> will create <code>foo_washed.jpg</code>. 86 example, processing <code>foo.jpg</code> will create <code>foo_washed.jpg</code>.
82 By default, the new file will be created in the same directory as the file 87 By default, the new file will be created in the same directory as the file
87 <h3>Configuring the Whitelist</h3> 92 <h3>Configuring the Whitelist</h3>
88 <p>There are two kinds of whitelist entries: those that match an entire 93 <p>There are two kinds of whitelist entries: those that match an entire
89 metadata key, and those that match a key prefix. The latter end in an 94 metadata key, and those that match a key prefix. The latter end in an
90 asterisk. The whitelist is case-sensitive; i.e. the entry <code>exif.image.colormap</code> 95 asterisk. The whitelist is case-sensitive; i.e. the entry <code>exif.image.colormap</code>
91 <em>will not</em> match the <code>Exif.Image.ColorMap</code> key.</p> 96 <em>will not</em> match the <code>Exif.Image.ColorMap</code> key.</p>
97 <h2>That’s about It</h2>
98 <p>ExifWasher does not, and probably never will, do anything but remove
99 extraneous metadata.</p>
100 <p>First, I have no desire to re-invent the wheel. There are already
101 excellent open-source tools like Gimp for image editing, and ExifTool and
102 Exiv2 for general-purpose metadata editing (in fact, ExifWasher is built
103 on top of Exiv2). If you need the functionality of some other tool,
104 download and use it!</p>
105 <p>Second (and more importantly), I want ExifWasher to be simple, and
106 therefore easy to learn and easy to use. The more challenging an
107 information-security tool is to use, the less likely it is to be used
108 frequently, and the more likely it is that compromising information gets
109 disclosed.</p>
92 </body> 110 </body>
93 </html> 111 </html>