Forum Replies Created

  • Re: Reply To: Mifare Plus S change sector AES keys

    12. April 2019 at 10:23
    in reply to: Mifare Plus S change sector AES keys
    Thanks for the answer.

    No, I didn't forget the second part, but if I feed in the auth second part the same 32 bytes that I compute for first authentication it's not ok, the card returns authentication error, that's why I think I must return something else and also not derive kenc/kmac again as this would go against the idea of a lighter form of authentication. However, I'm not sure what the second part looks like for following authentication.

    Unfortunately, all the datasheets that I can find with the name you mentioned have about 20 pages, they seem to be vastly shortened.
    + 0  |  - 0

    Re: Reply To: Mifare Plus S change sector AES keys

    11. April 2019 at 21:07
    in reply to: Mifare Plus S change sector AES keys
    Ok, I solved it, the keys can't be updated with write plain maced, they need to be written encrypted.

    I have another problem though, I can only use first authentication, afterwards I can't complete the challenge for the following authentication command. I'm probably missing a step or two. At the moment I'm working around it with resetting auth, but I'm not sure this is the correct way. How can I correctly use the challenge from following authentication, 0x76?
    + 0  |  - 0

    Re: Reply To: Mifare Plus S change sector AES keys

    11. April 2019 at 18:38
    in reply to: Mifare Plus S change sector AES keys
    Actually it seems the error code is "Current command code is not available at the current card state".
    + 0  |  - 0

    Re: Reply To: Mifare Plus S change sector AES keys

    11. April 2019 at 18:08
    in reply to: Mifare Plus S change sector AES keys
    Thanks for the answer.

    I am able to do personalization in SL0 and switch from SL1 to SL3 and also to read/write in SL3, but only with the keys that I personalized in the first step on a blank SL0 card.

    How can I change an AES sector key after authentication? In SL3 if I authenticate to sector 0x4000 and then write the new key to 0x4000 with write plain maced it doesn't seem to stay persistent, after poweroff/poweron of the card I still need to authenticate with the original key, the new key that I write in 0x4000 seems to be ignored.

    To be more exact, the problem is that we are in the process of requesting our Mifare Plus S cards to come personalized in SL1 instead of blank and in SL0, but we want to change the factory provided sector keys for security purposes and I'm not sure what the procedure is to change an AES key.
    + 0  |  - 0

    Re: Reply To: Problems switching Mifare Plus S 2K to SL1

    3. October 2018 at 10:04
    in reply to: Problems switching Mifare Plus S 2K to SL1
    Hi,

    I am already encapsulating 0xa8 and 0xaa command apdus in the "generic session" apdus according to Omnikey documentation, but it does not seem to work. I just thought that maybe someone faced the same problem.

    Thanks!
    + 0  |  - 0
Viewing 5 posts - 1 through 5 (of 5 total)