-
Notifications
You must be signed in to change notification settings - Fork 46
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
Move securedrop-proxy mimetypes to package #615
Move securedrop-proxy mimetypes to package #615
Comments
Currently, This behavior is what remained from past (pre 0.1.0) iterations, where the workstation relied on users downloading submissions and messages via Tor Browser and opening them manually. Since we now use the SecureDrop client, to handle file and message management, it might make sense to use the most defensive mimetype handler by default, the same one as |
This package supersedes and replaces the "securedrop-workstation-sd-svs-disp" package, see freedomofpress/securedrop-workstation#615
This package supersedes and replaces the "securedrop-workstation-sd-svs-disp" package, see freedomofpress/securedrop-workstation#615
@rocodes to fix. |
The mimetype associations added to the
sd-proxy
VM are currently configured via Salt, not via thesecuredrop-proxy
deb package, or any other package. As we work on template consolidation (#471), we should remove those mimetypes from salt and update the symlink-targeting logic introduced in #605.The text was updated successfully, but these errors were encountered: