public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Mem Wallet <memwallet.info@gmail.com>
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] standardize on bitcoin signed ecies ?
Date: Tue, 26 Aug 2014 18:08:02 -0700	[thread overview]
Message-ID: <CAAS2fgTV9hj1otAQZpF3tE+goNu591gj_mcoHrNCPBbVHuuz6Q@mail.gmail.com> (raw)
In-Reply-To: <CAKzHBKndU4nHHK=h4=G+hG_t_c77h0DHpeEUK+Kk9q2CsRHEcQ@mail.gmail.com>

On Tue, Aug 26, 2014 at 5:57 PM, Mem Wallet <memwallet.info@gmail.com> wrote:
>
> Does anyone see a value in a standardized PGP-style message,
> which would allow someone performing a bitcoin transaction to
> send signed encrypted messages using only public and private
> bitcoin keys ?
>
> I'd like to propose a signed encrypted message protocol, in case
> someone see's value in encoding such a thing into a BIP.

Using the same keys for signing and encryption is generally considered
a bad practice, for a number of reasons.

If the keys aren't the same, there is much less reason to use
something specific to Bitcoin.

Getting all the details right in an encryption implementation is very
difficulty, previously published efforts in Bitcoin software have been
_severely_ flawed and insecure. I am not confident that an effort
right now would receive adequate review.



      reply	other threads:[~2014-08-27  1:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-27  0:57 [Bitcoin-development] standardize on bitcoin signed ecies ? Mem Wallet
2014-08-27  1:08 ` Gregory Maxwell [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=CAAS2fgTV9hj1otAQZpF3tE+goNu591gj_mcoHrNCPBbVHuuz6Q@mail.gmail.com \
    --to=gmaxwell@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=memwallet.info@gmail.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