- From: Kingsley Idehen <kidehen@openlinksw.com>
- Date: Mon, 07 Oct 2013 08:42:22 -0400
- To: public-webpayments@w3.org
- Message-ID: <5252AC2E.3060103@openlinksw.com>
On 10/6/13 4:02 PM, Anders Rundgren wrote: > Exactly. > > And browser's were not designed for performing secure transactions either. > > That is, there is no foundation for payment standards in this space > unless you have some 10 years or so to spend. Browsers are poor tools for any kind of secure interaction with protected data. Even when they implement PKI, they ultimately get the UX/UI wrong. That said, and this is really important to understand, they are but one type of HTTP user agent. As the mobile space demonstrates, a Web Browser doesn't have totally own how end-users interact with HTTP accessible resources. Thus, we don't need to wait 10 years to fix this problem. The standards being discussed and shaped on this list will go a long way towards fixing this problem i.e., decoupling the solution from a specific type of HTTP user agent :-) -- Regards, Kingsley Idehen Founder & CEO OpenLink Software Company Web: http://www.openlinksw.com Personal Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca handle: @kidehen Google+ Profile: https://plus.google.com/112399767740508618350/about LinkedIn Profile: http://www.linkedin.com/in/kidehen
Attachments
- application/pkcs7-signature attachment: S/MIME Cryptographic Signature
Received on Monday, 7 October 2013 12:42:47 UTC