almet/dangerzone
1
0
Fork 0
mirror of https://github.com/freedomofpress/dangerzone.git synced 2025-04-28 18:02:38 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

Add work-in-progress disclaimer to readme

Browse source
This commit is contained in:
Micah Lee 2020-01-09 09:36:25 -08:00
parent e1d0163504
commit 2e7a8d2ecd
No known key found for this signature in database
GPG key ID: 403C2657CD994F73
1 changed files with 2 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -2,6 +2,8 @@
Take potentially dangerous PDFs, office documents, or images and convert them to a safe PDF. Take potentially dangerous PDFs, office documents, or images and convert them to a safe PDF.
_This is a work in progress and is not quite ready for daily use yet._
![Screenshot](./assets/screenshot.png) ![Screenshot](./assets/screenshot.png)
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 of RGB color values for each page. Then, in a separate sandbox, dangerzone takes this pixel data and converts it back into a PDF. 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 of RGB color values for each page. Then, in a separate sandbox, dangerzone takes this pixel data and converts it back into a PDF.