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

Explain name importation and its relevance to securely hosting .bit domains #4

Open
JeremyRand opened this issue Apr 26, 2014 · 1 comment

Comments

@JeremyRand
Copy link
Member

Name importation is important for securely hosting .bit domains, so it should be explained on the site.

Rough explanation (copied and pasted from an e-mail from me to indolering):

"If you need the ability to change the IP address from a hot wallet, the IP address should be in a dd/ name, which is imported into a d/ name. The d/ name should specify a TLS fingerprint, and should not be in a hot wallet. In the event that the hot wallet is compromised and the dd/ name is hijacked, your website will display a TLS error until you register a new dd/ name, but your .bit domain will not be stolen, and your visitors will not be MITM'ed (unless they're stupid enough to click through the TLS error)."

@phelixbtc
Copy link
Contributor

Should go into the wiki, too.

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

2 participants