- From: Anders Rundgren via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2017 06:29:25 +0000
- To: public-web-nfc@w3.org
@Liryna I fully understand what you want to do. The problem is that ISODep support would require an __exception_ from the Web Security Model in order to be practical_. This is a decision for the browser vendors, I'm just an independent technologist interested in NFC technology. OTOH, if you consider what a malicious site could do you will find that there is a bunch of potential security and privacy issues which at least I don't know how to cope with. That it works in the physical world is because you actually "see" the relying party (terminal, physical reader) which doesn't translate well to the Web with its billions of relying parties. Effectively, ISODep support presumes that the _user_ becomes the security mediator which is a hard sell these days. -- GitHub Notification of comment by cyberphone Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/101#issuecomment-305701460 using your GitHub account
Received on Friday, 2 June 2017 06:29:32 UTC