News for hackers. Stuff that matters.
Re:Maintaining digital certificate security by ryan-c on Tuesday July 08, 2014 @06:06PM (#8006969)
okTurtles is one of several middleware options that runs on top of Namecoin, implementing the domain record spec. It advocates using someone else's trusted server as a data source, but does not at this time implement any integrity protection for data in transit.

http://www.freespeechme.org/ is a more mature and more secure.

Edit: DNSChain does not appear to provide certificate validation for .bit domains in common browsers at this time. It can serve DANE records, but the browsers don't currently verify them and the existing browser extensions for adding DANE support require DNSSEC which DNSChain does not provide, unless I'm missing something.

Re:Maintaining digital certificate security by higherpurpose on Wednesday July 09, 2014 @06:21AM (#8008901)
I think DNSchain offers some compatibility with .bit domains, but the real innovation happens with .dns domains?
Re:Maintaining digital certificate security by itistoday2 on Monday July 14, 2014 @03:17PM (#8032657)
FreeSpeechMe is not practical for use because it requires running Namecoin locally.

DNSChain is just as secure as FreeSpeechMe when connected to a trusted DNSChain server.

> It advocates using someone else's trusted server

This is misleading. You and Jeremy keep repeating this line and it honestly feels like a vendetta at this point (I hope it's not). It advocates connecting to your DNSChain server (or a close friend's). This is security that is either on par with FreeSpeechMe (without the baggage), or orders of magnitude better than what's provided by HTTPS today.