News for hackers. Stuff that matters.
Re:How we found rogerkver’s obfuscated wallet private key by walrus01 on Tuesday October 24, 2017 @07:28PM (#15546098)
until you run into a government agency that thinks drawing a black box over something in a PDF is acceptable redaction, where the PDF is exported/published to the public in its full vector/metadata markup format, not a raster image... hilarious when you can just highlight and copy/paste to get whatever text is hidden. Have seen it several times.

be careful asking non technical employees, sans training, to "just draw a black box over it", is what I'm saying.

Re:How we found rogerkver’s obfuscated wallet private key by tedunangst on Tuesday October 24, 2017 @07:54PM (#15546217)
Apocryphally some places have a policy that all redacted documents must be printed then rescanned before release.
Re:How we found rogerkver’s obfuscated wallet private key by TeMPOraL on Wednesday October 25, 2017 @06:35AM (#15548935)
The govt should write themselves a virtual printer that would take in the data stream and output a PDF made of individual images. A typical print-to-PDF virtual printer, but government-sanctioned, and they could also make it do something like store the document in an audit database or whatever, just to give people a strong incentive not to skip it or use anything else.
Re:How we found rogerkver’s obfuscated wallet private key by pixl97 on Wednesday October 25, 2017 @11:14AM (#15550792)
It does open another risk of nation state style attacks that compromise the virtual print driver in a manner that it does not redact information, or encodes 'hidden' information into the format of the document. That seems easier to do with a digital print driver than with the messy digital to analog conversions that occur in a scanner/printer.
Re:How we found rogerkver’s obfuscated wallet private key by tedunangst on Wednesday October 25, 2017 @09:08AM (#15549741)
That would be interesting and not hard to setup. Install cups on some box, definitely not the host containing sensitive info, and you have a limited, auditable outbound channel.
Re:How we found rogerkver’s obfuscated wallet private key by cperciva on Tuesday October 24, 2017 @11:14PM (#15547158)
Doesn't that reveal the serial numbers of the printers they use?
Re:How we found rogerkver’s obfuscated wallet private key by joncrocks on Wednesday October 25, 2017 @04:26AM (#15548382)
They just print it again and re-scan. It's printers all the way down.
Re:How we found rogerkver’s obfuscated wallet private key by tedunangst on Wednesday October 25, 2017 @09:05AM (#15549722)
Maybe they don't care? Learning this was printed by the printer used for redacted info doesn't tell you much.
Re:How we found rogerkver’s obfuscated wallet private key by zaroth on Tuesday October 24, 2017 @11:08PM (#15547127)
Reality Winner missed that day at NSA training!
Re:How we found rogerkver’s obfuscated wallet private key by cesis on Tuesday October 24, 2017 @11:19PM (#15547186)
She did print it and probably was caught because of that

http://mashable.com/2017/06/06/printer-dots-nsa-leak.amp

Re:How we found rogerkver’s obfuscated wallet private key by walrus01 on Tuesday October 24, 2017 @08:00PM (#15546248)
because fuck you, trees! right?
Re:How we found rogerkver’s obfuscated wallet private key by simcop2387 on Tuesday October 24, 2017 @10:26PM (#15546920)
It's the simplest method to wipe out any metadata from the original document
Re:How we found rogerkver’s obfuscated wallet private key by Avshalom on Tuesday October 24, 2017 @08:34PM (#15546422)
Well if you can blur an arbitrary section you can, even if not black-black, just choose an average and write over everything with that (so adaptive grey).
Re:How we found rogerkver’s obfuscated wallet private key by davchana on Wednesday October 25, 2017 @02:01AM (#15547859)
Not in US, and certainly not in any agency, but anytime I black box something in a pdf, I print it back as image to PDF printer.
Re:How we found rogerkver’s obfuscated wallet private key by Someone on Wednesday October 25, 2017 @04:06AM (#15548312)
I may misinterpret what you mean by “print it back as image to PDF printer”, but I doubt that removes the text. When printing the document, the program likely will just render the text first, and the black box over it. Reason? To be able to skip rendering the text, the computer must know:

- a black box will get drawn over it. - that box completely covers the text. - that box will be drawn opaquely.

Verifying that isn’t easy.

Save to .png is safer. It doesn’t support layers, so what you see is what you get.

Re:How we found rogerkver’s obfuscated wallet private key by TeMPOraL on Wednesday October 25, 2017 @06:36AM (#15548946)
> Save to .png is safer. It doesn’t support layers, so what you see is what you get.

Just make sure your document->png converter doesn't do anything silly with the alpha channel.

Re:How we found rogerkver’s obfuscated wallet private key by Someone on Wednesday October 25, 2017 @11:48AM (#15551101)
It can be worse. Apparently, Adobe’s FireWorks writes bitmap layers and vector data to .png custom data chunks.
Re:How we found rogerkver’s obfuscated wallet private key by davchana on Friday October 27, 2017 @03:53AM (#15566472)
PDF-xChange keeps text as text if printed normally, completely selectable, vectorized, but changes and rasterises it to image if printed as image, pixelated and jpeg-ized. At about 200% zoom it is clearly visible that it is pixelated, and nothing else.