Re:Maintaining digital certificate security
by uwutnope on Tuesday July 08, 2014 @03:25PM
(#8006232)
You have to store the blockchain on your computer to be able to browse website securely via namecoin, if you use 'light wallets' you will end up with the same DNS as today (trust a third party DNS server + CA or Namecoin node). You could use http://convergence.io/ type of idea to connect to two trusted Namecoin nodes but do we really expect the average user to keep a list of trusted nodes?
[ Parent
| on HN ]
If you only want to be able to resolve against Namecoin, it's possible to build a client that stores only the unspent transaction output set for names and a few dozen recent blocks and full security.
Re:Maintaining digital certificate security
by uwutnope on Tuesday July 08, 2014 @08:12PM
(#8007442)
How does that scale in filesize if Namecoin had 215 million~ domain names like we have in the current ICANN system? Also, what would the solution be for smartphones, downloading even just a few blocks isn't preferable with phone networks.
You can have trustless namecoin without storing the blockchain, using techniques like SPV.
Re:Maintaining digital certificate security
by uwutnope on Tuesday July 08, 2014 @08:18PM
(#8007465)
According to https://en.bitcoin.it/wiki/Thin_Client_Security SPV relies on the trust of your ISP. When nodes send you the blockchain data, is that an encrypted transfer or open to MITM?