From: "Jeremy Spilman" <jeremy@taplink•co>
To: Wladimir <laanwj@gmail•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Positive and negative feedback on certificate validation errors
Date: Fri, 28 Feb 2014 23:50:32 -0800 [thread overview]
Message-ID: <op.xb09eip8yldrnw@laptop-air> (raw)
In-Reply-To: <CA+s+GJBD-L8Lz+dsEgL+_xzJbrqjC7z_9Z45ow=xoccxwEdssQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Fri, 28 Feb 2014 23:26:57 -0800, Wladimir <laanwj@gmail•com> wrote:
> Such a thing would be interesting for a future BIP standard. I see one
> problem here: for an unsigned payment request there isn't really an
> "origin". >Browser URI handlers don't send the referrer either.
Yeah, good point. If you have a cert, we have the CN from the cert, which
becomes the string displayed as 'Pay To' and alternatively 'Merchant'.
But if there's no cert then all you have is memo.
So the best way to differentiate signed requests is by prominently
displaying that Merchant string. Really the green part should just be the
'Pay To' line, the rest is content. If it showed a BLANK 'Pay To' that
would make the lack of certificate highly apparent.
[-- Attachment #2.1: Type: text/html, Size: 1091 bytes --]
next prev parent reply other threads:[~2014-03-01 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 6:26 Jeremy Spilman
2014-03-01 7:26 ` Wladimir
2014-03-01 7:50 ` Jeremy Spilman [this message]
2014-03-02 10:37 ` Mike Hearn
2014-03-02 7:52 ` [Bitcoin-development] Payment Protocol Hash Comments Jeremy Spilman
2014-03-02 8:44 ` Mike Hearn
2014-03-02 8:52 ` Drak
2014-03-02 10:39 ` Mike Hearn
2014-03-03 12:39 ` Drak
2014-03-02 18:18 ` [Bitcoin-development] Positive and negative feedback on certificate validation errors Troy Benjegerdes
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=op.xb09eip8yldrnw@laptop-air \
--to=jeremy@taplink$(echo .)co \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@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