ISLOG Logon (Windows NFC Login)
-
@Maxime-C. said in ISLOG Logon (Windows NFC Login):
ial version is required (but it can be discussed, we had to start from so
other text entries do not cause the issue, and using ASUS NFC express instead of ISLOG does not cause the issue. however i agree its a weird issue and may not be the fault of your app.
-
Hi Again @Maxime-C, I now have a brand new phone, I got a Samsung S7 (cheap now that the 8 is almost out) and remarkably this situation is still happening.
If the tag has a text string on it created by your software, when I unlock my phone it still launches the fitbit app.
I didn't even do a phone backup / restore from one phone to the next. I made it a clean build feeling it was time for a phone clean-up.
This was on a brand new phone with no history.
-
@jasok2 I don't see any reason for that. Probably the way we encode credential information and the way FitBit detect the tag which is similar. I don't know if this is documented somewhere on FitBit?
Otherwise a new 4.8.0515 version was released (minor bug fixes release) ;).
-
I am having a problem writing to the tag. NTAG216 ISLOG recognizes a new tag and is setup for PCSC and the PICC port.
Which cards or tags are you having success with?
-
@Maxime-C. I have been surfing the FitBit forum, apparently other people are also having issues with any NFC tag that has an entry as an encrypted text file. I suspect its an issue with the FITBIT app.
Although as a future feature suggestion it would be awesome if the ISLOG Logon application could just recognise the NFC crards ID and unlock the computer based on that so that nothing needed to be written to the ring at all.
-
@jasok2 said in ISLOG Logon (Windows NFC Login):
@Maxime-C. I have been surfing the FitBit forum, apparently other people are also having issues with any NFC tag that has an entry as an encrypted text file. I suspect its an issue with the FITBIT app.
Although as a future feature suggestion it would be awesome if the ISLOG Logon application could just recognise the NFC crards ID and unlock the computer based on that so that nothing needed to be written to the ring at all.
Would just card ID be secure enough? NXE NTAG2xx have a read/write
protect to secure usernames and passwords past page 0 and 1 (the card id).I love the NFC Ring for swimming pool terminal access and refreshment payments. Swimsuit tags get lost or fall off diving.
-
@rcourtney said in ISLOG Logon (Windows NFC Login):
Would just card ID be secure enough?
Is just a key secure enough for your house ?
I believe so, this is exactly how Android does it with Trusted devices and how many digital door locks work with NFC key fobs etc.
So long as you can easily delete a lost ring from having access to your computer I think this would in fact be the best way.
-
@rcourtney we tested it mainly on Mifare Ultralight C and Mifare DESFire EV1 but NTAG should be ok. Gonna test it later.
@jasok2 ok thanks for the FitBit feedback. Nothing to do on our side then. Concerning using the CardID only, ISLOG Logon product do support that but only on the Enterprise version. NFC Community version requires to write on the tag, I believe it should be ok for most individuals no?
-
@Maxime-C. said in ISLOG Logon (Windows NFC Login):
NFC Community version requires to write on the tag, I believe it should be ok for most individuals no?
@Maxime-C I can say 100% there no requirement from the NFC ring users for for our version to write on the tag. it would be much better if it did not write on the tag, so that the tag can be used for other things.
Also please keep in mind the new payments ring, there is a chance that we will not be able to write on that ring, If that happens your program will no longer work :(
so please please in future versions make it work without writing on the ring, just like android trusted devices and the Samsung door locks.
-
@rcourtney I'm having the same issue with Ultralite-C card and a Mifare Classic using the default Windows PCSC drivers. Maybe there's a special format they need to be using?
-
