From: Mike Hearn <mike@plan99•net>
To: Wendell <w@grabhive•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Simple contacts exchange (was: Social network integration (brainstorm))
Date: Tue, 17 Sep 2013 14:36:29 +0200 [thread overview]
Message-ID: <CANEZrP2Ewq4+xT+FCaB_U64QNSW-QA6SooUus+Ad0=DNbh-erA@mail.gmail.com> (raw)
In-Reply-To: <2BC93E25-27D2-474E-842D-6684E96E9472@grabhive.com>
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
The payment protocol doesn't *require* signed certificates, it just gives
the option of using them.
However if you don't have some kind of cryptographic proof of identity,
what stops me putting your name and face into my payment requests and
claiming to be you?
[-- Attachment #2: Type: text/html, Size: 340 bytes --]
next prev parent reply other threads:[~2013-09-17 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 15:07 Wendell
2013-09-06 22:47 ` Eric Lombrozo
2013-09-16 14:05 ` Wendell
2013-09-17 9:30 ` Wendell
2013-09-17 10:03 ` Mike Hearn
2013-09-17 12:05 ` Wendell
2013-09-17 12:36 ` Mike Hearn [this message]
2013-09-07 21:44 ` Mike Hearn
2013-09-09 7:26 ` Wendell
2013-09-09 11:43 ` Mike Hearn
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='CANEZrP2Ewq4+xT+FCaB_U64QNSW-QA6SooUus+Ad0=DNbh-erA@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=w@grabhive$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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