Reply To: KeyA and KeyB and how to protect the contacless card from cloning?

Forum MIFARE general topics and applications KeyA and KeyB and how to protect the contacless card from cloning? Reply To: KeyA and KeyB and how to protect the contacless card from cloning?

Re: KeyA and KeyB and how to protect the contacless card from cloning?

16. February 2016 at 10:50
Hi,

After you have changed the keys in the sector trailer, any access needs an authentication with one of the new keys first. The access condition bytes let you either key A or key B for protecting this sector. A third person have to check with all possible key combinations to get a successful authenticate.

Cloning means to make a copy from each memory location. For copying each sector you need the keys. If you NOT use the default key, your data is protected. But take in mind: to use the card for more than one purpose is also a use case. Let us assume for example, you have an application for an access system in sectors 2 and 3. Then you can have a debit account on you card for the cafeteria in sector 4. The cafeteria maintainer knows his own sector keys, but not yours (and vice versa). So you would not block all other sectors for using and the cafeteria maintainer also not.

The MIFARE Classic uses a built-in encryption. This is supported by most of the reader manufacturers. The encryption algorithm cannot be changed. If you want to use e.g. DES, Triple-DES or AES encryption, you have to use one of our other products like the MIFARE Plus or the MIFARE DESFire.

For any contactless reader you use, there are driver files available for all desktop operating systems. Theses drivers implement the key management and the encryption. You have to look into the user manual or the developer guide how to use the interface.

I do not know the driver you want to use, but also for Linux there are drivers available. The widely used interface is the so called PC/SC interface. There is a port to Linux available, called PCSC-Lite.

The MIFARE Team
+ 0  |  - 0