From: Matt Whitlock <bip@mattwhitlock•name>
To: Thomas Zander <thomas@thomaszander•se>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Does anyone have anything at all signed by Satoshi's PGP key?
Date: Mon, 15 Sep 2014 11:51:35 -0400 [thread overview]
Message-ID: <3205491.XcafbkJRvW@crushinator> (raw)
In-Reply-To: <3586037.E6tZxYPG6n@coldstorage>
On Monday, 15 September 2014, at 5:10 pm, Thomas Zander wrote:
> So for instance I start including a bitcoin public key in my email signature.
> I don't sign the emails or anything like that, just to establish that everyone
> has my public key many times in their email archives.
> Then when I need to proof its me, I can provide a signature on the content
> that the requester wants me to sign.
That would not work. You would need to sign your messages. If you were merely attaching your public key to them, then the email server could have been systematically replacing your public key with some other public key, and then, when you would later try to provide a signature, your signature would not verify under the public key that everyone else had been seeing attached to your messages.
next prev parent reply other threads:[~2014-09-15 16:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 13:55 Peter Todd
2014-09-13 14:03 ` Jeff Garzik
2014-09-14 6:28 ` Peter Todd
2014-09-15 7:23 ` Thomas Zander
2014-09-15 9:49 ` Melvin Carvalho
2014-09-15 13:08 ` Jeff Garzik
2014-09-15 13:32 ` Brian Hoffman
2014-09-15 14:33 ` Jeff Garzik
2014-09-15 14:49 ` Brian Hoffman
2014-09-15 14:55 ` Pieter Wuille
2014-09-15 14:38 ` ThomasZander.se
2014-09-15 15:10 ` Thomas Zander
2014-09-15 15:51 ` Matt Whitlock [this message]
2014-09-15 16:07 ` Thomas Zander
2014-09-15 16:10 ` Gregory Maxwell
2014-09-15 16:20 ` Peter Todd
2014-09-15 14:44 ` Venzen
2014-09-15 18:06 ` Justus Ranvier
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=3205491.XcafbkJRvW@crushinator \
--to=bip@mattwhitlock$(echo .)name \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=thomas@thomaszander$(echo .)se \
/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