You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the software queries the UID of the Tag to gain access.
When a user stores the ID (by registering their Tag) the reader/writer could also write a value to the NDEF record of that Tag.
This would ensure if the ID is skimmed the users NDEF would also need to be skimmed and replicated to gain access. It would also mean if the users ID is skimmed and the user is aware then the user can just rewrite the NDEF value which means the hardware doesn't need to be replaced.
The caveat is if (and we should know this early on) that overwritiing the NDEF Record contents will overwrite any content on there IE vCard or contact details..
I've just exposed access to the NDEF section to my service so I'll have to do some investigation as to how that data is structured. Ideally I'd be able to write a guid as a text record without interfering with any data already written to the tag.
Add optional NDEF records for additional security.
The text was updated successfully, but these errors were encountered: