Take potentially dangerous PDFs, office documents, or images and convert them to safe PDFs
Find a file
2022-09-13 13:17:22 +01:00
.circleci replace automated test code in CI 2022-09-13 13:17:15 +01:00
assets Resize screenshots 2021-11-24 16:04:06 -08:00
container don't type check dev scripts 2022-08-22 12:28:48 +01:00
dangerzone fix type hints for gui-common (CI would fail) 2022-09-13 13:17:20 +01:00
dev_scripts sort imports with isort linter 2022-08-22 10:15:26 +01:00
install Enforce code style 2022-08-26 14:12:01 -07:00
share bump version (0.3.2) & append to CHANGELOG.md 2022-08-25 09:23:40 +01:00
tests migrate to pytest & test_docs -> tests/test_docs 2022-09-13 13:07:58 +01:00
.gitignore migrate to pytest & test_docs -> tests/test_docs 2022-09-13 13:07:58 +01:00
BUILD.md Updates to the macOS and Windows build scripts and documentation 2022-08-26 14:06:06 -07:00
CHANGELOG.md Add missing entry in 0.3.2 changelog 2022-09-07 05:46:48 -04:00
LICENSE Remove useless files from dangerzone-converter, and move files out of separate scripts directory 2021-11-24 12:47:39 -08:00
Makefile report non-containerized code coverage 2022-09-13 13:17:22 +01:00
poetry.lock report non-containerized code coverage 2022-09-13 13:17:22 +01:00
pyproject.toml report non-containerized code coverage 2022-09-13 13:17:22 +01:00
README.md Update download links to 0.3.2 in readme 2022-09-06 10:27:40 -07:00
RELEASE.md Updates to the macOS and Windows build scripts and documentation 2022-08-26 14:06:06 -07:00
setup-windows.py sort imports with isort linter 2022-08-22 10:15:26 +01:00
setup.py sort imports with isort linter 2022-08-22 10:15:26 +01:00
stdeb.cfg Remove requests dependency 2022-08-19 15:16:14 +01:00

Dangerzone

Take potentially dangerous PDFs, office documents, or images and convert them to a safe PDF.

Settings Converting

Dangerzone works like this: You give it a document that you don't know if you can trust (for example, an email attachment). Inside of a sandbox, Dangerzone converts the document to a PDF (if it isn't already one), and then converts the PDF into raw pixel data: a huge list of RGB color values for each page. Then, in a separate sandbox, Dangerzone takes this pixel data and converts it back into a PDF.

Read more about Dangerzone in the blog post Dangerzone: Working With Suspicious Documents Without Getting Hacked.

Getting started

You can also install Dangerzone for Mac using Homebrew: brew install --cask dangerzone

Some features

  • Sandboxes don't have network access, so if a malicious document can compromise one, it can't phone home
  • Dangerzone can optionally OCR the safe PDFs it creates, so it will have a text layer again
  • Dangerzone compresses the safe PDF to reduce file size
  • After converting, Dangerzone lets you open the safe PDF in the PDF viewer of your choice, which allows you to open PDFs and office docs in Dangerzone by default so you never accidentally open a dangerous document

Dangerzone can convert these types of document into safe PDFs:

  • PDF (.pdf)
  • Microsoft Word (.docx, .doc)
  • Microsoft Excel (.xlsx, .xls)
  • Microsoft PowerPoint (.pptx, .ppt)
  • ODF Text (.odt)
  • ODF Spreadsheet (.ods)
  • ODF Presentation (.odp)
  • ODF Graphics (.odg)
  • Jpeg (.jpg, .jpeg)
  • GIF (.gif)
  • PNG (.png)

Dangerzone was inspired by Qubes trusted PDF, but it works in non-Qubes operating systems. It uses containers as sandboxes instead of virtual machines (using Docker for macOS, Windows, and Debian/Ubuntu, and podman for Fedora).

Set up a development environment by following these instructions.