Forum Replies Created

  • Re: Reply To: Error – SAM without Antenna OR a faulty CL Reader, after upgrading RFIDDiscover

    7. February 2019 at 15:01
    in reply to: Error – SAM without Antenna OR a faulty CL Reader, after upgrading RFIDDiscover
    Hi,
    Thank you. Yesterday the NXP RFIDDiscover team has published a new version (4.6.0.0) to fix the error mentioned here. I've test it with success.
    Claudio.
    + 0  |  - 0

    Re: Reply To: Error – SAM without Antenna OR a faulty CL Reader, after upgrading RFIDDiscover

    29. January 2019 at 16:11
    in reply to: Error – SAM without Antenna OR a faulty CL Reader, after upgrading RFIDDiscover
    Hi,
    I've verified that de DIP 1 is (and was) in 'ON' positio for SAM operation in S-MODE but the error persists.
    The same reader work well with 4.3.0.0 version of the RFIDDiscover Tool.
    I'll very appreciate any help.
    Thank you & regards
    + 0  |  - 0

    Re: Reply To: Functional Specifications MIFARE SAM AV2 1645xx

    8. August 2017 at 17:01
    in reply to: Functional Specifications MIFARE SAM AV2 1645xx
    Thank you for your answer.
    I've have request this docuement and I couldn't find it on docstor.
    And yes, our company has NDA signed with NXP.
    Thank you and regards,
    Claudio
    + 0  |  - 0

    Re: Reply To: Mifare authentication string

    3. August 2017 at 1:38
    in reply to: Mifare authentication string
    Hi,

    Authenticating with MIFARE Classic is a process comprised by three stages.
    1. You should SELECT the Card in RF field from the reader
    2. AUTHENTICATING TO A SECTOR (16 in a 1K MIFARE Classic Card) with a properly key (The so called "transport key" by default, is 0xff ff ff ff ff ff -six bytes long-)
    3. READING AND/OR WRITING FROM/TO A REGISTER of 16 Bytes (3 effective register for data by sector, except the sector 0, which has 2 effective records, because the firs one is a read only Manufacturer Block; and one sector trailer record, in which the secrets key and the sector access conditions bits resides).

    NOTE1: The authentication process should be done every time you need change from one sector to another.
    NOTE2: The select process should be done every time the authentication process fails.
    NOTE3: Each reader has its own command syntax.

    To write an interfase you should have acces: to the reader commands protocol, to the command set of the reader, and of course, the datasheet of the Card. (A good staring point is the MF1 IC S50 Functional specifications).

    Regards,
    Claudio


    + 0  |  - 0

    Re: Reply To: 8-byte CMAC

    2. August 2017 at 19:29
    in reply to: 8-byte CMAC
    Hello,
    The problem was solved.
    As you said before, the error was in the implementation of the algorithm.
    Thank you and regards,
    Claudio
    + 0  |  - 0

    Re: Reply To: 8-byte CMAC

    2. August 2017 at 16:17
    in reply to: 8-byte CMAC
    Hello again,

    Yes, I am using the information on page 17, (Secret key (Kx) = 01020304050607080910111213141516), and as a message the one specified in step 4 (c8e7f707 455e194f 015e7f35 03000000), paddes to 16 bytes.


    The enrollment algorithm is based on AES128 and corroborates that specified by the documentation of Ref. 23 and Ref. 24 of document DS164535 ("P5DF081 MIFARE secure access module SAM AV2."). That is, the output data corroborates all the examples presented in the NIST document 800-38B.

    Obviously, there is some detail, or process, that I am not following correctly. If possible, please refer me to any documents I can use to solve the CMAC calculation.

    Thank you again and regards,

    Cladio
    + 0  |  - 0

    Re: Reply To: 8-byte CMAC

    2. August 2017 at 14:35
    in reply to: 8-byte CMAC
    Thank you for your answer.

    I followed the referred NIST calculation algorithms 800-38B by AN1823 and DS 164555 and reproduced correctly the cited examples. But, I do not get from AN1823 3.1.3.1., Step 4, reproduce the result you describe (A509E6108ADBDB49CC831A02680DE82E). I attached the exits of my test program:

    --------------------------------------------------
    K 01020304 05060708 09101112 13141516

    Subkey Generation
    AES_128(key,0) c7fa1346 528c9a2e f2026f8e 095f7273
    K1 d2c13e19 b9c613a9 02c0615a debee461
    K2 a5827c33 738c2752 0580c2b5 bd7dc845

    Example 2: len = 8
    M c8e7f707 455e194f 015e7f35 03000000
    AES_CMAC 5bc95519 d3050dea 3cdf9abb 41349dac

    Example 2: len = 16
    M c8e7f707 455e194f 015e7f35 03000000
    AES_CMAC abe61493 d592fd1d dc4f6d82 ca336308

    Any help will be appreciate.
    Thank you.
    Claudio

    + 0  |  - 0

    Re: Reply To: SAM_LockUnlock error switching a virgin MIFARE SAM AV2 from AV1 to AV2 Mode

    2. August 2017 at 14:12
    in reply to: SAM_LockUnlock error switching a virgin MIFARE SAM AV2 from AV1 to AV2 Mode
    Hi Christ,
    Please, could you give me the specific page in AN1823 on which the calculation procedure is indicated?
    Thank you and best regards.
    Claudio
    + 0  |  - 0
Viewing 8 posts - 1 through 8 (of 8 total)