From: Pavol Rusnak <stick@gk2•sk>
To: Chris D'Costa <chrisjdcosta@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] cryptographic review requested
Date: Wed, 22 Oct 2014 10:52:01 +0200 [thread overview]
Message-ID: <54477031.8040200@gk2.sk> (raw)
In-Reply-To: <CAC0TF=mi5WUHf5wvU0YDOSuUiyrEUH_+QVNGTBr_RYQEzY7QYw@mail.gmail.com>
On 10/22/2014 10:46 AM, Chris D'Costa wrote:
> Looks great, but how would you resolve the problem of knowing for certain
> that the public key you have received to encrypt the message is not from a
> MITM?
Isn't this the same problem with PGP?
--
Best Regards / S pozdravom,
Pavol Rusnak <stick@gk2•sk>
next prev parent reply other threads:[~2014-10-22 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 21:12 Mem Wallet
2014-10-21 20:56 ` Pavol Rusnak
[not found] ` <CAC0TF=mi5WUHf5wvU0YDOSuUiyrEUH_+QVNGTBr_RYQEzY7QYw@mail.gmail.com>
2014-10-22 8:52 ` Pavol Rusnak [this message]
2014-10-22 14:56 ` Pavol Rusnak
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=54477031.8040200@gk2.sk \
--to=stick@gk2$(echo .)sk \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=chrisjdcosta@gmail$(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