-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update "How it works" section and add some articles about Dangerzone #39
Conversation
Add the results of our latest security audit, as well as some articles from journalism-related media, which mention the use of Dangerzone.
Update the "How it works" section, since it was out of sync with the recent developments on Dangerzone.
baad530
to
7939fb8
Compare
Heads up, I've converted the changes in this PR from HTML to Markdown, to make them work for 11ty. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple of nits but mostly LGTM! Should we wait with merging this until freedomofpress/dangerzone#748 lands? AIUI this describes the post-748 architecture.
Actually, with this PR we describe the architecture we have currently (minus the gVisor parts which will be covered in #41). We still refer to the second container in the section of how Dangerzone works, and the fact that we mount the pixel data in it. Once we merge freedomofpress/dangerzone#748, we'll have to update it once more. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Update the "How it works" section, since it was out of sync with the recent developments on Dangerzone. Also, add the results of our latest security audit, as well as some articles from journalism-related media, which mention the use of Dangerzone.
See also freedomofpress/dangerzone#807