Skip to content
This repository has been archived by the owner on Jan 7, 2024. It is now read-only.

Adapt SecureDrop SDK to SecureDrop Proxy Behavior #16

Closed
eloquence opened this issue Sep 4, 2018 · 2 comments
Closed

Adapt SecureDrop SDK to SecureDrop Proxy Behavior #16

eloquence opened this issue Sep 4, 2018 · 2 comments

Comments

@eloquence
Copy link
Member

eloquence commented Sep 4, 2018

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.

@eloquence eloquence changed the title Adapt SecureDrop SDK to SecureDrop Proxy Changes Adapt SecureDrop SDK to SecureDrop Proxy Behavior Sep 4, 2018
@kushaldas
Copy link
Contributor

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.

@redshiftzero
Copy link
Contributor

@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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants