-
Notifications
You must be signed in to change notification settings - Fork 39
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
Confine securedrop-proxy with apparmor #1889
Labels
Comments
16 tasks
I tried to do this today but |
I had much more success writing the profile by hand by following https://gitlab.com/apparmor/apparmor/-/wikis/Profiling_by_hand - not fully tested PR incoming. |
legoktm
added a commit
that referenced
this issue
May 28, 2024
Because this is a static Rust binary, it ends up being super simple, we just need to import the abstractions for DNS, OpenSSL and TLS certs. Fixes #1889.
8 tasks
github-project-automation
bot
moved this from In Progress
to Done
in SecureDrop dev cycle
Jun 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the proxy v2 architecture, it should be relatively straightforward for us to confine the proxy under apparmor, as it needs no file access and should only be making outbound requests on port 80/443.
The text was updated successfully, but these errors were encountered: