Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use NDEF records for additional Security (Sesame Stretch Goal) #4

Open
Lokki-P opened this issue Mar 4, 2016 · 3 comments
Open

Use NDEF records for additional Security (Sesame Stretch Goal) #4

Lokki-P opened this issue Mar 4, 2016 · 3 comments

Comments

@Lokki-P
Copy link
Collaborator

Lokki-P commented Mar 4, 2016

Add optional NDEF records for additional security.

@maz-net-au
Copy link
Collaborator

As in, store another token (guid or something)? or the actual login details? or something else?

@JohnMcLear
Copy link
Contributor

NDEF is the user writable space on an NFC Tag.

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..

@maz-net-au
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants