public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99.net>
To: Mark Friedenbach <mark@monetize.io>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Merge avoidance and P2P connection encryption
Date: Fri, 13 Dec 2013 13:49:23 -0800	[thread overview]
Message-ID: <CANEZrP00qF+cikCe8_j6YY9Y5_meQkFMvh+BNeK0ZZYtvS2XjQ@mail.gmail.com> (raw)
In-Reply-To: <52AB5DA9.1060701@monetize.io>

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

>
> Or alternatively, the user-signed payment request without iteration
> count is enclosed within a payr.com-signed envelope that contains the
> iteration count.


But how does that show up in the user interface? I don't know how you would
explain what the signature means or implies, or what you do if the
signature is broken/missing.

The only thing that a maliciously modified iteration count can do is cause
money to be sent to an address that's beyond the recipients gap limit,
meaning they won't receive it (unless they reconfigure their software and
rescan). But you can't steal money that way.

[-- Attachment #2: Type: text/html, Size: 873 bytes --]

      reply	other threads:[~2013-12-13 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 16:03 [Bitcoin-development] Merge avoidance and P2P connection encryption Mike Hearn
2013-12-12 17:28 ` Paul Rabahy
2013-12-12 18:24   ` Mike Hearn
2013-12-13  0:20     ` Gavin Andresen
2013-12-13  0:26       ` Jeff Garzik
2013-12-13 14:43         ` Peter Todd
2013-12-13 17:26       ` Mike Hearn
2013-12-13 19:19         ` Mark Friedenbach
2013-12-13 21:49           ` Mike Hearn [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=CANEZrP00qF+cikCe8_j6YY9Y5_meQkFMvh+BNeK0ZZYtvS2XjQ@mail.gmail.com \
    --to=mike@plan99.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=mark@monetize.io \
    /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