public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: "Ryan X. Charles" <ryan@bitpay.com>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 proposed changes
Date: Wed, 5 Mar 2014 11:18:41 +0100	[thread overview]
Message-ID: <CANEZrP3mUnU9h20V_Ss_FH0md91PnKhUTKmuM_8rPPuZuvjdJA@mail.gmail.com> (raw)
In-Reply-To: <5303B110.70603@bitpay.com>

[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]

>
> On an unrelated note, X.509 is a terrible standard that should be
> abandoned as quickly as possible. BitPay is working on a new standard
> based on bitcoin-like addresses for authentication. It would be great if
> we could work with the community to establish a complete, decentralized
> authentication protocol. The sooner we can evolve beyond X.509 the better.


Because this is such a common sentiment, I wrote a couple of articles on
the matter.

The first is about why BIP 70 uses the SSL PKI and an examination of the
most commonly proposed alternative ideas:

   https://medium.com/p/b64cf5912aa7

... including the web of trust, using bitcoin addresses/the block chain,
allowing multiple certs, trust-on-first-use and (for SSL only)
perspectives/convergence.

The second is a summary of some of the most famous crypto-usability
research papers published in the past 10-15 years. They cover SSL and PGP.
If you're interested in designing alternatives, reading these papers would
be a good place to start:

    https://medium.com/p/d04ea6a2c771

There's a book from O'Reilly called Security & Usability that contains 34
papers and essays. It's very good:

   http://shop.oreilly.com/product/9780596008277.do

[-- Attachment #2: Type: text/html, Size: 1910 bytes --]

      parent reply	other threads:[~2014-03-05 10:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 17:31 [Bitcoin-development] BIP70 proposed changes Andreas Schildbach
2014-02-18 19:14 ` Ryan X. Charles
2014-02-18 20:15   ` Gavin Andresen
2014-02-18 21:40   ` Andreas Schildbach
2014-02-19 14:10     ` Jeff Garzik
2014-02-19 16:44       ` Mike Hearn
2014-05-06  2:35       ` Odinn Cyberguerrilla
2014-05-06  8:22         ` Alon Muroch
2014-02-18 21:47   ` Peter Todd
2014-02-18 23:41     ` Bernd Jendrissek
2014-02-18 22:02   ` Derber
2014-02-21 15:34   ` Mike Hearn
2014-03-05 10:18   ` Mike Hearn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CANEZrP3mUnU9h20V_Ss_FH0md91PnKhUTKmuM_8rPPuZuvjdJA@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=ryan@bitpay.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox