From: "Luke-Jr" <luke@dashjr.org>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Message Signing based authentication
Date: Sun, 3 Nov 2013 00:33:55 +0000 [thread overview]
Message-ID: <201311030033.56983.luke@dashjr.org> (raw)
In-Reply-To: <CAJfRnm6Jbm+6__zgvodAroDWRugyX_4atHH1k4+U9_1-GLThjw@mail.gmail.com>
On Sunday, November 03, 2013 12:29:28 AM Allen Piscitello wrote:
> This was one of my concerns when implementing a scheme where you sign a
> refund transaction before the original transaction is broadcast. I
> originally tried to pass a hash and have the server sign it. However, I
> had no way to know that what I was signing wasn't a transaction that was
> spending my coins! So I changed the code to require sending the full
> transaction, not just the hash. The other way to mitigate this is through
> not having any unspent outputs from this key.
Well, there's no use case to sign with an address that has already been sent
coins. The main problem with enforcing this is that you can't exactly stop
someone from sending to an "identity" address.
Luke
next prev parent reply other threads:[~2013-11-03 0:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-02 5:01 [Bitcoin-development] Message Signing based authentication bitcoingrant
2013-11-02 5:54 ` Luke-Jr
2013-11-02 13:02 ` Mike Hearn
2013-11-02 13:16 ` Melvin Carvalho
2013-11-02 13:19 ` Hannu Kotipalo
2013-11-02 16:26 ` Mike Hearn
2013-11-02 16:26 ` Mike Hearn
2013-11-02 16:52 ` Melvin Carvalho
2013-11-02 17:08 ` Jeff Garzik
2013-11-02 17:16 ` Hannu Kotipalo
2013-11-02 21:14 ` Johnathan Corgan
2013-11-02 21:51 ` Mark Friedenbach
2013-11-03 0:29 ` Allen Piscitello
2013-11-03 0:33 ` Luke-Jr [this message]
2013-11-03 1:19 ` Allen Piscitello
2013-11-03 1:27 ` Luke-Jr
2013-11-03 1:36 ` Allen Piscitello
2013-11-03 6:23 ` Timo Hanke
2013-11-06 3:38 ` Melvin Carvalho
2013-11-02 21:57 ` slush
2013-11-06 3:01 ` Melvin Carvalho
2013-11-06 6:41 ` slush
2013-12-06 10:44 ` Melvin Carvalho
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=201311030033.56983.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-development@lists.sourceforge.net \
/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