stronglink | A searchable , syncable , content-addressable notetaking | Hashing library

by btrask C Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | stronglink Summary

stronglink is a C library typically used in Security, Hashing applications. stronglink has no bugs, it has no vulnerabilities and it has medium support. However stronglink has a Non-SPDX License. You can download it from GitHub.

StrongLink is a notetaking/blogging system that supports search and sync. You can use content addresses (hash links) to link between entries, regardless of where they were created or where they’re being viewed. Currently, entries can’t be edited after they’ve been written, which you can think of like writing in ink.

Support

Quality

Security

License

Reuse

Support

stronglink has a medium active ecosystem.

It has 1042 star(s) with 45 fork(s). There are 42 watchers for this library.

It had no major release in the last 6 months.

There are 92 open issues and 19 have been closed. On average issues are closed in 75 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of stronglink is current.

Quality

stronglink has 0 bugs and 0 code smells.

Security

stronglink has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

stronglink code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

stronglink has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

stronglink releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 1227 lines of code, 44 functions and 49 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of stronglink

Get all kandi verified functions for this library.

stronglink Key Features

No Key Features are available at this moment for stronglink.

stronglink Examples and Code Snippets

No Code Snippets are available at this moment for stronglink.

Community Discussions

Trending Discussions on stronglink

Mifare PlusX 4K: is there a consistent but unique part of the key that can be used for identification without authentication?

QUESTION

Mifare PlusX 4K: is there a consistent but unique part of the key that can be used for identification without authentication?

Asked 2020-Feb-24 at 04:35

I am trying to write a PC application (Windows, .NET) that identifies students on the basis of some card equipped with RFID identification to build lecture attendance registers. Currently I have a Stronglink SL040A RFID reader (http://www.stronglink-rfid.com/en/rfid-modules/sl040.html), which operates as a HID and sends the data as a series of keystrokes.

The system works perfectly with older cards like Mifare 1K classic (even with PayPass credit cards). The new student cards (and identity cards) issued by the Hungarian authorities, however, contain Mifare PlusX 4K chips, which seem to send a new key every time one uses the card. I have tried experimenting with the settings the configuration tool of the reader offers, but to no avail. I can make the 1K classic cards send a much longer key by changing the end block parameter but the PlusX 4K keeps sending the shorter, and painfully non-consistent, keys.

I am a physicist without a deeper understanding of these chips and RFID authentication in general – I am just trying to make a job done that seemed easy at the beginning. I have no intention of cracking or abusing these cards in any way, I am just trying to find some block of data on the card that stays consistent upon each use, does not require complicated authentication protocols but is unique between different cards.

Is it possible or is it against the philosophy of these chips? If possible, shall I have to buy a new reader or can I make it do what I need?

Your thoughts are much appreciated.

...

ANSWER

Answered 2020-Feb-24 at 04:35

From the MiFare PlusX 4K datasheet:

Section 8.2: There are three different versions of the PICC. The UID is programmed into a locked part of the NV-memory reserved for the manufacturer:
• unique 7-byte serial number
• unique 4-byte serial number
• non-unique 4-byte serial number
Due to security and system requirements, these bytes are write-protected after being programmed by the PICC manufacturer at production.
...
During personalization, the PICC can be configured to support Random ID in security level 3. The user can configure whether Random ID or fixed UID shall be used. According to ISO/IEC 14443-3 the first anticollision loop (see Ref. 5) returns the Random Number Tag 08h, the 3-byte Random Number and the BCC, if Random ID is used. The retrieval of the UID in this case can be done using the Virtual Card Support Last command, see Ref. 3 or by reading out block 0.

From what you have described, it appears that the cards are running in Security Level 3, and unfortunately, the backwards-compatible part of the card only exists at lower security levels. The mentioned command of Virtual Card Support Last is also only available after level 3 authentication.

I'm afraid what you want to do appears impossible unless you can use the ISO/IEC 14443-4 protocol layer, which I think would let you authenticate at level 3? The relevant data appears to be in section 8.7, and involves AES authentication.

Source https://stackoverflow.com/questions/60247096

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install stronglink

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: