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

Create a SD Directory Server to Audit and Enumerate instances #258

Closed
Hainish opened this issue Jan 15, 2014 · 3 comments
Closed

Create a SD Directory Server to Audit and Enumerate instances #258

Hainish opened this issue Jan 15, 2014 · 3 comments

Comments

@Hainish
Copy link
Contributor

Hainish commented Jan 15, 2014

This has been discussed in #92 (comment) - create a third party directory server to periodically scrape the SD instances out there, checking all active resources for malicious code injection using a standardized hashing mechanism. If an instance is modified, alert the SD instance owner of the change.

The entire SD application can live in a JS browser application, but the one component that would still have to be provided by the server is the GPG key of the instance. Thus the directory server should have a copy of the keys and check that the public key of the system is the same as well.

@garrettr
Copy link
Contributor

I have a proposal for verifying and auditing journalist's public keys in the draft 1.0 Roadmap. @Hainish Would appreciate your feedback! It is quite different from the proposal here, but satisfies the same goals.

@ghost ghost added the ops/deployment label Dec 7, 2017
@ghost
Copy link

ghost commented Dec 7, 2017

@conorsch is this resolved in the upcoming securedrop.org version ?

@conorsch
Copy link
Contributor

@dachary Thanks for the ping!

Yes, the forthcoming overhaul of securedrop.org will implement an automated scanner for both the Source Interface and the Landing Page for each known SecureDrop instance, similar in style to Secure The News. The development effort on the new scanner is ongoing, and we optimistically hope to ship in Q2 2018.

As such, I'm closing this issue, as the final pieces are close to completion, and no code changes will be required to this repository in order to finalize implementation.

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

No branches or pull requests

3 participants