From: Mike Hearn <mike@plan99•net>
To: Jeremy Spilman <jeremy@taplink•co>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70 extension to allow for identity delegation
Date: Sun, 2 Mar 2014 11:44:00 +0100 [thread overview]
Message-ID: <CANEZrP0bkyO=L_9RAbgGCXhWSn+Tc_F12tMxqVz9d0Vd=kaU8w@mail.gmail.com> (raw)
In-Reply-To: <op.xb3btqp7yldrnw@laptop-air>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
>
> Perhaps the UI just isn't expressive enough currently to expose this
> situation in any way, let alone reliably alert the user to the issue,
> because there's no way for the payment processor to get authenticated
> fields other than memo into the UI.
>
I think for now as long as payment processors include the merchant name in
the memo, that's good - as long as hardware devices or second factor
wallets display the memo as well! Trezor has a small screen, I don't know
how feasible displaying the whole memo is there though - hence an interest
in something better. For now we can probably muddle through.
> A poor solution: If the UI included some sort of certificate viewer, even
> just tied to the OS certificate viewer, and made the cert available for
> inspection, at least the merchant would have a chance to put some fields in
> there which a very advanced user might actually find.
>
Not really interested in solutions that only help very advanced users.
Besides, my understanding is that most PKI CA's will not sign certs that
include arbitrary data they don't understand for I guess the obvious
security reasons (generally signing things you don't understand is a bad
idea). But I've never actually tried it.
We don't want anyone to have to go back to their CA anyway, especially not
with special requests.
[-- Attachment #2: Type: text/html, Size: 1782 bytes --]
next prev parent reply other threads:[~2014-03-02 10:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 11:46 Mike Hearn
[not found] ` <1393704464.6290.118.camel@mimiz>
2014-03-01 20:42 ` Kevin Greene
2014-03-02 10:57 ` Mike Hearn
2014-03-02 10:38 ` Jeremy Spilman
2014-03-02 10:44 ` Mike Hearn [this message]
2014-03-02 15:20 ` Andreas Schildbach
2014-03-02 16:14 ` Mike Hearn
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='CANEZrP0bkyO=L_9RAbgGCXhWSn+Tc_F12tMxqVz9d0Vd=kaU8w@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jeremy@taplink$(echo .)co \
/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