{"action":"reopened","issue":{"url":"https://api.github.com/repos/freedomofpress/securedrop/issues/2841","repository_url":"https://api.github.com/repos/freedomofpress/securedrop","labels_url":"https://api.github.com/repos/freedomofpress/securedrop/issues/2841/labels{/name}","comments_url":"https://api.github.com/repos/freedomofpress/securedrop/issues/2841/comments","events_url":"https://api.github.com/repos/freedomofpress/securedrop/issues/2841/events","html_url":"https://github.com/freedomofpress/securedrop/issues/2841","id":287983807,"number":2841,"title":"Enable multiple organizations to share one SecureDrop ","user":{"login":"redshiftzero","id":7832803,"avatar_url":"https://avatars3.githubusercontent.com/u/7832803?v=4","gravatar_id":"","url":"https://api.github.com/users/redshiftzero","html_url":"https://github.com/redshiftzero","followers_url":"https://api.github.com/users/redshiftzero/followers","following_url":"https://api.github.com/users/redshiftzero/following{/other_user}","gists_url":"https://api.github.com/users/redshiftzero/gists{/gist_id}","starred_url":"https://api.github.com/users/redshiftzero/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/redshiftzero/subscriptions","organizations_url":"https://api.github.com/users/redshiftzero/orgs","repos_url":"https://api.github.com/users/redshiftzero/repos","events_url":"https://api.github.com/users/redshiftzero/events{/privacy}","received_events_url":"https://api.github.com/users/redshiftzero/received_events","type":"User","site_admin":false},"labels":[{"id":192539755,"url":"https://api.github.com/repos/freedomofpress/securedrop/labels/app","name":"app","color":"bfe5bf","default":false},{"id":96394577,"url":"https://api.github.com/repos/freedomofpress/securedrop/labels/feature","name":"feature","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-01-12T01:50:27Z","updated_at":"2018-04-18T10:53:14Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"## Description\r\n\r\nThis would be a big change and would require careful thought and planning, but I think this feature could be safely used primarily in the case of a media conglomerate (there might be others but this is the use case it would be designed for). They have a central legal department and admin staff. They have several media properties all of which have journalists that want SecureDrops. As is standard with SecureDrop, they would host the SecureDrop servers on prem. Only the administrators of the central media conglomerate would have SSH access to the servers. All other users would access the journalist interface only. \r\n\r\nThere would need to be a per-media conglomerate submission key. Journalists from each news organization would access a separate inbox for that news organization. \r\n\r\nMuch of this could be done in the web application (we would obviously need to do a schema migration). On the ops side, we'd probably want to shift away from Ansible entirely for the submission key management and manage the submission key(s) instead via the admin interface. Management of the news organizations would also come up: what if an organization wants to join or leave SecureDrop? We'd need to enable the deletion of media organizations. Via the admin interface there should be a way for each new news organization in the conglomerate that wants SecureDrop access to add:\r\n\r\n* The name of the org\r\n* A logo\r\n* The public key that submissions should be encrypted to\r\n\r\nFor each journalist user, the admin should specify which news organization submissions they should have access to. This would also be configured via the admin interface. \r\n\r\n### Possible flow\r\n\r\n1. Source signs in, they are taken to a page with the logos of all news organizations.\r\n2. They select the organization they wish to leak to. Submissions will be encrypted to that news organization's key. \r\n3. Journalists sign in, see only the documents intended for the organization they are a part of, and they download them and decrypt them on their per-organization SVS using their per-organization key. \r\n\r\n### Landing pages\r\n\r\nThe landing page at each news organization of the conglomerate would point to the onion address. There could also be a new route on the source interface that specifies the org, e.g. https://blah.onion/organization/exampletimes - this could enable sources to skip the organization selection page. \r\n\r\n## User Stories\r\n\r\nAs a media conglomerate with multiple news organizations interested in SecureDrop (not all with skilled administrators) I want to safely allow all my news organizations to securely receive leaked documents and messages. "}}
{"actor":{"display_login":"heartsucker"}}