You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 7, 2024. It is now read-only.
The SecureDrop Qubes OS proxy modifies requests with non-JSON responses (see https://github.com/freedomofpress/securedrop-proxy) - it uses qvm-move for those submissions. The SecureDrop SDK has to account for this behavior.
The text was updated successfully, but these errors were encountered:
eloquence
changed the title
Adapt SecureDrop SDK to SecureDrop Proxy Changes
Adapt SecureDrop SDK to SecureDrop Proxy Behavior
Sep 4, 2018
I think this part should be done by the proxy itself. For example, when the proxy gets a call to download a file, it will use the SDK API to download the file and then will use qvm-* command to move it to the right vm.
I will add an example below after getting back online.
@kushaldas and I discussed this last week, and we decided that since securedrop-proxy has been completed and is ready to be packaged as discussed in freedomofpress/securedrop-workstation#107, we'll proceed with implementing the current plan for the MVP
The SecureDrop Qubes OS proxy modifies requests with non-JSON responses (see https://github.com/freedomofpress/securedrop-proxy) - it uses
qvm-move
for those submissions. The SecureDrop SDK has to account for this behavior.The text was updated successfully, but these errors were encountered: