- From: Anders Rundgren via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Jun 2017 13:02:21 +0000
- To: public-web-nfc@w3.org
> NFC is ISO7816. That's why this issue exists. web-nfc is already giving access to the device by allowing to send NFCMessage @Liryna To be perfectly honest I actually _do not understand_ how the current scheme can be more secure than ISODep since the browser doesn't (AFAICT...), have any insights in the applications using NDEF. That is, the latter could indeed be arbitrarily sensitive. Maybe the authors could shed some light on this? Anyway, the numerous problems in this space is also why I'm advocating a _dedicated_, _locked-down_, _write-only_ Web-NFC variant, intended as a direct replacement for _inconvenient_ and _security-broken_ QR codes. -- GitHub Notification of comment by cyberphone Please view or discuss this issue at https://github.com/w3c/web-nfc/issues/101#issuecomment-305779976 using your GitHub account
Received on Friday, 2 June 2017 13:02:28 UTC