[J253]

To prevent some of the issues with blurring or compression leaking sensitive info, one simple workaround I’ve used is to just put black boxes over the text as usual in any program and then take a screenshot and save it out from there. No accidental history or compression leaking.

[addaon]

One thing that still leaks is the exact spacing between words adjacent to the black boxes. This is a particular concern one only one or two words are blacked out -- for example a name. With a known font (with known character widths and kerning tables) and a known text engine applying those kerning rules, there's often very few combinations of letters that give the exact pixel (or subpixel) width blank space.

[lelandfe]

Clever. Monospaced fonts improve things, with the tradeoff of making it trivial to know the number of characters redacted.

[8note]

For a first name + last name combination, you still have a lot of potential combinations based on the total length

[toomanydoubts]

Has someone made a demo of that?

[bobsmooth]

So blurring can be reversed and black bars can be cracked, is there any way to securely redact a document?

[Gigachad]

Tbh I think there needs to be some dedicated tool for censoring images. Even with this method there is a small chance that it isn’t 100% opaque. I have seen several images where you can pull them in to gimp and adjust the color levels until even the slightest color difference becomes blown out and you can read the censored text.

It’s just too easy to mess this stuff up.

[8note]

Windows paint does pretty well, though it's still error prone

[anamexis]

That would be a cool idea for a really simple and easily auditable FOSS image tool.