Skip to content
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

Closed
legoktm opened this issue Mar 4, 2024 · 2 comments · Fixed by #2039
Closed

Confine securedrop-proxy with apparmor #1889

legoktm opened this issue Mar 4, 2024 · 2 comments · Fixed by #2039
Assignees
Labels

Comments

@legoktm
Copy link
Member

legoktm commented Mar 4, 2024

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.

@legoktm
Copy link
Member Author

legoktm commented May 22, 2024

I tried to do this today but aa-genprof didn't really work, it generated all the log events but processed them for the profile. Will spend a bit more time poking at it before trying something else.

@legoktm
Copy link
Member Author

legoktm commented May 28, 2024

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.
@legoktm legoktm self-assigned this May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant