@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?
@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) ;).
@MarkGabb thanks for asking. I don't want to be too commercial here as this thread is about the community version so I will keep it short. NFC community version apart, there is a standalone version and a client / server version. Pricing is per user or per workstation depending what is cheaper for the customer. Additional one-time cost for the server. Until now our main business was in France and border countries for this product line. Hospitals are indeed a good part of our market (with a card today, not a ring). We generally provide installation and support services to complete a project successfully. I believe there is such opportunities on other countries too. I'm not sure about the ring here, some establishments ask caregivers to remove their jewelry before to start working.
Thanks @jasok2. There is nothing specific on your data. I don't know well how FITBIT works but maybe they try to do something as soon there is a text record on the tag?
The solution is tested on Windows 7, 8, 8.1 and 10. Works on any edition (family, professional...)
The commercial version is used on few tablets by customers but this NFC community version should works on it too.
Only local accounts are supported for NFC Community edition, this is a restriction on the community version to ensure it is used for personal use. If you want to use a domain the commercial version is required (but it can be discussed, we had to start from somewhere ^^).
@jasok2 this is weird and not excepted. What the text record written by ISLOG Logon looks like? Any chance you can copy/past here (if you're using a test password, otherwise try to change it to a test password and confirm this is still happening)? Thank you.
Ok... well we will see if this is happening again to someone and investigate further at this moment.
I created a webpage for the solution to have an unique place where to get latest version, see http://www.islog.com/en/software/islog-logon-nfc-community/
Please feel free to suggest anything else if you believe it is missing. I hope you enjoy it otherwise ;)
Ok, good to know everything is working properly now.
I also believe this could come from the fact you didn't waited long enough before removing the ring from the reader. It is safe to keep it around 1sec on the reader.
I will wait for more feedback and provide an official release with dedicated web page. Thanks for your tests!
Small update that remove 'beep' on logon, and add data encryption on nfc tag.
Stored nfc text record is now AES-128 encrypted with a random key generated at first tag use, XORed with tag UID, and base64 encoded for convenience purpose.
No changes about @jasok2 current issue.
You can download it here :
64-bit: http://download.islog.com/islog/4.0/NG/ISLOG Logon NFC Community-4.7.0713-x64.exe
32-bit: http://download.islog.com/islog/4.0/NG/ISLOG Logon NFC Community-4.7.0713-x86.exe
@jasok2 Thanks for the logs.
It looks like it is incomplete, did you truncated it at the beginning or forgot to restart ISLOGService service?
Otherwise maybe your reader just disappears for an unknown reason, you could also give a try with ReadCard analyze tool community version which is using the same RFID/NFC middleware (LibLogicalAccess). If your reader / tag disappears on ReadCard after a while, then the issue is on the middleware or the reader.
Thank you.
This works on my side even after 1 hour of inactivity. Does your computer entered sleep mode?
Otherwise you can also enable logs by setting HKEY_LOCAL_MACHINE\SOFTWARE\ISLOG\LogsCardPlugin registry key to c:\islogcards.log, then restart ISLOGService service, reproduce the issue and share your log file (please indicate time of the issue reproduction).
@jasok2 how long did you wait to reproduce it on your last test?
Thanks for the global positive feedback @Lokki and @jasok2.
I will investigate your lock tag detection issue as this should work properly. It could maybe be an issue with this specific reader I will give a try as I also have it.
There is indeed no encryption on stored data for now but this will be quickly added as it is not a technical issue. Beep is a default feature that cannot be disable on current configuration UI but maybe it will just be disabled by default depending on feedback.
For additional information about NFC reader type, acr122 can work as a PC/SC reader or as an NFC reader (technically, it's libnfc supported readers here in this case). But on Windows it requires specific libusb driver installation so it's generally preferable to use PC/SC.
I'm cross-posting with https://forum.nfcring.com/topic/683/nfc-reader-writer-for-windows/20 as this thread is about the same topic.
I'm Maxime from ISLOG and we just put John's advices in practice (he tried our RFID Logon solution months ago and wasn't completely pleased with it previous state).
ISLOG Logon is now available freely for personal use under ISLOG Logon NFC Community package.
You can download it here :
64-bit: http://download.islog.com/islog/4.0/NG/ISLOG Logon NFC Community-4.7.0708-x64.exe
32-bit: http://download.islog.com/islog/4.0/NG/ISLOG Logon NFC Community-4.7.0708-x86.exe
This is a first version for feedback, please be gentle :). No data encryption for now but it will come.
It unfortunately cannot be open-sourced because we have to re-architecture a lot the current codebase to do so (some modules are shared with our commercial product) which is too much investment for our small team right now. So except there is something like thousands of requests we will not do it, sorry. Small comfort, part of it is already open source like the RFID / NFC middleware https://github.com/islog/liblogicalaccess
EDIT: see https://forum.nfcring.com/topic/782/islog-logon-windows-nfc-login
@johnyma22 said in NFC reader/writer for windows:
Hey guys just an update on this, I have been working w/ a third party to put together a solution for us. The experience w/ ACR122 & other readers is exceptional. This will take months to materialize so please be patient :) The third party afaik don't offer a consumer usage license yet so that's what I'm going to try to negotiate for NFC Ring Owners.
Nice to be mentioned!
I'm Maxime from ISLOG and we just put John's advices in practice.
Our product ISLOG Logon is now available freely for personal use under ISLOG Logon NFC Community package.
EDIT: for latest version to download, please go to http://www.islog.com/en/software/islog-logon-nfc-community/
This is a first version for feedback, please be gentle :).
-Thread forked from NFC reader/writer for windows by Andreas