dangerzone

Or, you know, instead of burning tokens/trees we could use a well established project instead ;) https://github.com/freedomofpress/dangerzone

(Hi, dangerzone maintainer here) There is indeed a dangerzone-cli tool¹, and it should be made more visible. We plan on updating/consolidating our docs in the foreseeable future, to make things clearer. Also, plans are here to make it possible to use dangerzone as a library, which should help use cases like the one you mention. ¹ https://github.com/freedomofpress/dangerzone/blob/main/dange...

https://github.com/freedomofpress/dangerzone/blob/main/dange... How hard did you look the other times?

Have you thought about some type of preprocessing to make the PDFs "simpler"? https://github.com/freedomofpress/dangerzone does something like that in its first stage.

This looks better than q(ubes)-pdf, but still not ideal. Seems that PyMuPDF is used with a fixed (single pathname) "/tmp/input_file" ? https://github.com/freedomofpress/dangerzone/blob/main/dange... Everything else is tossed through LibreOffice. Meanwhile what I'd prefer for PDFs is some allow-listed set of 'safe' PDF operations (layout image, layout text) to be used with sanitized inputs (no underflows, overflows, corruption, etc), and the results of any at snapshot-runtime code evaluated and then flattened out to a safe element. Image OCR could be run atop that. Similarly it'd be nice if a filter like that existed for the other documents, but as an individual contributor I don't have the human power to keep up with that goal and would take the same low hanging fruit worse but secure output route.

Related: https://dangerzone.rocks/ https://github.com/freedomofpress/dangerzone > Take potentially dangerous PDFs, office documents, or images and convert them to safe PDFs. From the learn more about page: > Dangerzone was inspired by TrustedPDF but it works in non-Qubes operating systems, which is important, because most of the journalists I know use Macs and probably won’t be jumping to Qubes for some time. > It uses gVisor sandboxes running in Linux containers to open dangerous documents, instead of virtual machines. And it also adds some features that TrustedPDF doesn’t have: it works with any office documents, not just PDFs; it uses optical character recognition (OCR) to make the safe PDF have a searchable text layer; and it compresses the final safe PDF. Previously (announcement and details of gVisor sandboxing etc): Safe Ride into

Rather than a PDF reader, how about a PDF sanitizer? I've heard of Dangerzone [1][2], though I've never used it. [1] https://github.com/freedomofpress/dangerzone [2] https://dangerzone.rocks/

I don't have experience with Qubes in order to know what the files do, but this repo references two files in a qubes directory: e.g. https://github.com/freedomofpress/dangerzone/blob/v0.6.0/qub...

start here: https://github.com/freedomofpress/dangerzone i've never used it, but i've been meaning to check it out. at least it should give you a jumping off point for further investigation. if that is insufficient, use proofpoint. for archives that are tickling bugs, you have to use a similar technique. it's not enough to analyze them and send them on as-is. you have to unpack in a sandbox (which will be detectable, no 2 ways about it, but the question is will anyone expend enough effort to detect -- no, not for your use case, seeing as how you're asking the question at all), process with dangerzone or dangerzone-like tool, then re-archive it and let the user see only that new archive.

I've read about the concept of "trusted PDFs" [1] from Qubes OS and the Dangerzone project [2]. I noticed people saying they use such tools to open applicant attachments in the context of employee hiring processes. Isn't it simpler to just open these untrusted files in a cloud service like Google Drive or Microsoft Office online? [1] https://blog.invisiblethings.org/2013/02/21/converting-untrusted-pdfs-into-trusted… [2] https://github.com/freedomofpress/dangerzone

You can use something similar on macOS, Windows or Linux, based on Docker containers, see Dangerzone: https://github.com/freedomofpress/dangerzone

Check out DangerZone. It encodes a .pdf (and other formats) to image data then converts it back to .pdf, optionally preserving OCR'ed text, so that any potential executable code hidden within is lost. For further security, all operations run sandboxed. https://github.com/freedomofpress/dangerzone