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

Deploy HTTPS for all of New Yorker website #10

Closed
ioerror opened this issue May 16, 2013 · 2 comments
Closed

Deploy HTTPS for all of New Yorker website #10

ioerror opened this issue May 16, 2013 · 2 comments

Comments

@ioerror
Copy link

ioerror commented May 16, 2013

An attacker may MITM the original connection to the New Yorker website. As a result, the attacker may change the .onion URL in transit. An attacker is able to see that the submitter isn't reading the New Yorker and if they download the Tor Browser as their next action, I suspect the attacker may simply choose to break connections to the Tor website. This will stop a potential submission and it also presents the attacker with an opportunity to insert malware (at download time) to discover the documents under consideration for submission.

@djon3s
Copy link

djon3s commented May 16, 2013

The other attack would be to generate a unique .onion address for every request being MiTM'd and correlate the IP of the New Yorker domain request with the .onion visited by the submitter.

@bitsteak
Copy link
Contributor

This is an issue with the New Yorker, not with DeadDrop. In addition, the New Yorker can distribute the correct onion address to potential sources through a variety of methods including verbally, on business cards, in printed media, etc to mitigate this risk. That said, the New Yorker has been informed.

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

No branches or pull requests

3 participants