On Fri, Dec 16, 2011 at 08:03:28AM -0800, Rick Wesson wrote: > Hardening the protocols and usability are related. Please look at some > of the work done in the IETF which has a long history in addressing > many of the issues you are considering. Review some of the elegance in > the bitcoin protocols. The proposals in this thread are neither clear > nor elegant. If you can't reach nearly the same level of > sophistication then I suggest you rethink your scheme.
That's why you use URI + bitcoin address pairs, and use SSL communication authenticated using the respective bitcoin pubkey. They may spoof your DNS server, they can't fake having the requested corresponding private key. Obviously, this moves the problem to getting the URL + address securely to the client that wants to interact with it, but that is inevitable if you're not going to rely on a pre-trusted certificate authority and PKI. Also, the client software can cache the address corresponding to a particular server or URL, making it similar to an ssh client that caches host keys and warns when they change. -- Pieter ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
