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.

Sign up for GitHub

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

Jump to bottom

Investigate adding SSL #9

Open
zancas opened this issue Oct 22, 2014 · 3 comments
Open

Investigate adding SSL #9

zancas opened this issue Oct 22, 2014 · 3 comments
Assignees
@zancas
Labels
help wanted question

Comments

@zancas
Copy link
Contributor

zancas commented Oct 22, 2014 •
edited by john-light
Loading

@dionyziz is curious about encryption and authentication for the lookups...

Clearly implementing a robust authentication mechanism using signed messages from the queried blockchain is an essential next step, should we think about HTTPS (self signed?) for encryption?

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
@taoeffect
Copy link
Member

@zancas I addressed this here I believe:

#6 (comment)

  1. Connection will be HTTPS self-signed cert.
  2. Verified using the above mechanism (constructor will take a fingerprint for the cert).
  3. DNSChain must add HTTPS support first as per comment: Unit test for invalid HTTPS cert #6 (comment)

@zancas zancas self-assigned this Oct 22, 2014
@zancas
Copy link
Contributor Author

zancas commented Oct 22, 2014

OK, the link you posted in #6: https://stackoverflow.com/questions/18122843/verify-certificates-fingerprints will be a great starting point for this.

@taoeffect
Copy link
Member

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zancas zancas

Labels
help wanted question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@taoeffect @zancas