Forum Replies Created

  • Re: Reply To: Cannot create DESFire EV1 aplication with AES key

    14. July 2016 at 21:36
    in reply to: Cannot create DESFire EV1 aplication with AES key
    Thank you a lot. Using your sample I complete it.

    It looks the problem was with bKeySet value. The helper method formatApplicationKeySettingTwo works in some unclear way...

    I think many people will say thank you next days for this sample!
    + 0  |  - 0

    Re: Reply To: Cannot create DESFire EV1 aplication with AES key

    14. July 2016 at 13:44
    in reply to: Cannot create DESFire EV1 aplication with AES key
    Hello.

    Our development is blocked by this problem :(
    Is there any workable sample how to personalize blank DESFire card with AES keys?
    + 0  |  - 0

    Re: Reply To: Cannot create DESFire EV1 aplication with AES key

    13. July 2016 at 14:59
    in reply to: Cannot create DESFire EV1 aplication with AES key
    Unfortunately first application authenticate with DESFireEV1.AuthType.AES does not work as well.

    + 0  |  - 0

    Re: Reply To: Cannot create DESFire EV1 aplication with AES key

    13. July 2016 at 13:56
    in reply to: Cannot create DESFire EV1 aplication with AES key
    Below is sample i created according to your instructions (except PICC Master key is changed before creating new application) and it does not work. Authentication for new application fails. Does some workable sample exist which uses AES keys?
    Please NOTE: if I don't change auth type from default to AES then it work fine. My question is EXACTLY about AES keys in application.


    byte appKeySettings1 = card.formatApplicationKeySettingOne((byte)1,
    IDESFireEV1.KSONE_APP_MKEY_CHANGABLE, IDESFireEV1.KSONE_CONFIG_CHANGABLE, IDESFireEV1.KSONE_FILE_DEL_NO_MKEY, IDESFireEV1.KSONE_GET_NO_MKEY);
    byte appKeySettings2 = card.formatApplicationKeySettingTwo((byte)2, IDESFireEV1.KSTWO_AES, false);

    card.selectApplication(0);
    card.authenticate(DESFireEV1.AuthType.Native, Sam.NxpKey.DEF_KEY.ordinal(), (byte) 0, 0, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);
    card.changeKey(0, Sam.NxpKey.DEF_KEY.ordinal(), (byte) 0, Sam.NxpKey.PICC_KEY.ordinal(), (byte) 0, DESFireEV1.KeyType.AES, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);

    card.authenticate(DESFireEV1.AuthType.AES, Sam.NxpKey.PICC_KEY.ordinal(), (byte) 0, 0, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);

    card.createApplication(AID, appKeySettings1, appKeySettings2);

    card.selectApplication(AID);

    card.createFile(0, new DESFireFile.StdDataFileSettings(DESFireEV1.CommunicationType.Plain, 0, 0, 1, 1, 8));

    // Next line fails both with AuthType.Native and AuthType.AES
    card.authenticate(DESFireEV1.AuthType.Native, Sam.NxpKey.DEF_KEY.ordinal(), (byte)0, 0, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);

    card.changeKey(0, Sam.NxpKey.DEF_KEY.ordinal(), (byte)0, Sam.NxpKey.AP_KEY.ordinal(), (byte)0, DESFireEV1.KeyType.AES, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);
    card.authenticate(DESFireEV1.AuthType.AES, Sam.NxpKey.AP_KEY.ordinal(), (byte)0, 0, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);

    card.authenticate(DESFireEV1.AuthType.Native, Sam.NxpKey.DEF_KEY.ordinal(), (byte)0, 1, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);
    card.changeKey(1, Sam.NxpKey.DEF_KEY.ordinal(), (byte)0, Sam.NxpKey.AP_KEY.ordinal(), (byte)0, DESFireEV1.KeyType.AES, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, IKeyConstants.DIV_OPTION_NODIVERSIFICATION, null);



    + 0  |  - 0

    Re: Reply To: Mifare SDK security

    3. July 2015 at 19:34
    in reply to: Mifare SDK security
    Hi,

    We are creating application which often run offline for all the event. This is one of customer requirements.
    In this case MIFARE SDK Lite starts to alert about one-time registration and moreover stop running at all.

    We know that it should happen just at first run but the world is not ideal and there ware cases when we were needed to cleanup application and install it. This causes the situation when terminal stopped to work!!!

    This is unacceptable for our business for two reasons:
    1. We cannot rely on solution which can stop to work at some point at all.
    2. Customer must not see any warning messages which does not relate to its business.

    We are ready to get paid version in case it will work offline and will not show any alerts.
    Is there a solution at Mifare for our case?

    Best regards,
    Alexey Tikhvinskiy,
    ArrowPass, Inc.
    + 0  |  - 0
Viewing 5 posts - 1 through 5 (of 5 total)