Forum Replies Created

  • Re: Reply To: Analyzing the License Verification Failure

    8. August 2023 at 17:10     in reply to: Analyzing the License Verification Failure

    fsurleau
    Ok, with the right package name, it works.
    My bad.
    + 0  |  - 0

    Re: Reply To: Analyzing the License Verification Failure

    7. August 2023 at 17:10     in reply to: Analyzing the License Verification Failure

    fsurleau
    Dear "The TapLinx team"

    It does NOT Work ! At all !

    With good network ( very good network ! ) I have the message : "Unable to complete the post to server" 99.999 % of time.

    Offline Key does not work, with or without network.

    By the way, isActivityRegistered() returns true, but it's not true...

    I Use library version 3.1.0.

    Regards,
    Frédéric Surleau
    + 0  |  - 0

    Re: Reply To: Picking the right key for DESFire EV2 cards when UIDs are unreliable/unavailable

    25. November 2022 at 16:10     in reply to: Picking the right key for DESFire EV2 cards when UIDs are unreliable/unavailable

    fsurleau
    Hi,

    The purpose of a random UID is to prevent a badge from being trackable.

    If the badge contains an open-access file containing a unique identifier, don't you think that some might consider that this introduces a security flaw ?
    + 0  |  - 0

    Re: Reply To: Problem to change PICC master key settings (AES).

    25. February 2016 at 16:55     in reply to: Problem to change PICC master key settings (AES).

    fsurleau
    Ok I found my problem.

    The CRC32 is calculated on CMD + KeySettings

    My CRC32 algorithm was correct, but it has to be sent LSB first.

    In my example :
    CRC32( 0x54 0x0B ) => D8 AC 23 F7 (not F7 23 AC D8 !)
    + 0  |  - 0

    Re: Re: mifare Appid

    31. October 2014 at 16:53     in reply to: mifare Appid

    fsurleau
    Thank you very much Luukvdo !

    I tried this, but it didn't worked, so I supposed the Lite API had limitations.

    But off course you're right.

    Regards.
    + 0  |  - 0

    Re: Re: mifare Appid

    30. October 2014 at 15:25     in reply to: mifare Appid

    fsurleau
    Bytes of APPID are the 3 first bytes of the sector to read/write
    After format, it should be 0x00, 0x00, 0x00.

    The lite API is only a demo. The full API will not have this APPID limitation with functions like authenticateSectorWithKeyA(int sectorIndex, byte[] key) and readBlock(int blockIndex)

    Hope the full API will be released soon...
    + 0  |  - 0
  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)