From 502ab9112a7624dbd7c1c90c2e12ed45512b8b3c Mon Sep 17 00:00:00 2001 From: mmauv <99472743+mmauv@users.noreply.github.com> Date: Wed, 28 Jun 2023 22:51:43 +0200 Subject: Add EMV functionality (#1080) * Add basic strcture needed for EMV implementation * Add demo EMV functionality with C code pasted in a very dirty and unsafe way. NOT FINAL * Refactor IccExtractor Structure * Fix Makefile * fix include file * move global variables from h to c * revert to memcpy * fix icc data recovery functions * Add EMV functionalities on windows * Make EMVToken structures like SecurityToken * Define constants instead of hard coded values * Token structures created with inheritance * refactor TokenKeyfile to use inherit. + polymor. * add Token.h + Token.cpp in modules in VS2010 * Add a comment at each use of SecurityToken class or objects * SecurityTokenKeyfilesDialog preparation * Implemennt GetAvailableTokens in Token class on windows * merge * up (patching for Windows) * foreach Token.cpp corrected * Display EMV keyfiles on first window in graphic interface * Add token to Windows UI * EMVToken selection on OKButton on Linux * Keyfile.cpp optimization * Move getKeyfileData in the token class * EMV::Token GetAvailableKeyfiles() base * Move getKeyfileData in the token class on unix * Remove test comments * Warnings resolved * RemoveeSecurityTokenLibraryNotInitialized exception if at least one emv token is detected * Adding new files * Remove old files and add the new version to the windows project * Change make_shared to shared_ptr constructor * IccExtractor integration working on linux * Throwing card not EMV execption * catch error when not EMV type in EMVToken::GetAvailableKeyfiles * Change types to compile on windows * list all keyfiles, security keyfiles and emv keyfiles in command line * Change type to be coherent and remove old todo comments * Remove todo comments * Change indentation and resolve a bug from previous commit * Use polymorphism for GetKeyfileData and add export option for EMVTokens on Linux * Linux : Allow to export EMV Tokens in command lines, Windows : Disable the delete button when EMV Keyfiles are selected * Remove SlotId from TokenInfo as it is already in Token * Correct errors on Linux * Disable delete option if one EMV Token is selected on Linux * Fix bug enabling delete button if nothing is selected * emv data used as reference then burnt * use of normal files in linux corrected * help updated * help updated for export functionnality * option EMV added to graphic interface but not yet working * Bug fix : Allow to use multiple EMV on windows * EMV Option added to UserPreferences * EMV Option working for Linux * EMV option added to Windows (not working yet) * [NOT TESTED] EMV option for Windows * Working EMV option on Windows * EMV Option for data extraction working for volume creation * EMV Option for data extraction working for Mount * EMV Option for data extraction working for mounting favorites volumes * EMV Option for extraction working for Changing volume password, Set Derivation Key Algorithm and Add or remove keyfile from volume * Windows : re-checking EMV Option when getting data * Removing error catches in the IccDataExtractor classe (It only throws error now). Changing GetPan signature to resemble the other functions signatures more * Changing EMV errors - Only throwing ICCExtractionException from outside of the ICC module. - Catching all TLVExceptions and PCSCExceptions to throw the right ICCExtractionException - Deleting APDU exceptions. * First version of the documentation * Adding function pointers for winscard library (but it crashes VeraCrypt) * Debugging function pointers * The import of the library on windows work as expected now * Reverting EMVToken.cpp changes used to test to library import * Searching for the System32 path instead of hard codding it * Fixing the bug were VeraCrypt crashes if there is no readers when "add Token files" is clicked * Winscard library not initialized in object constructor anymore to delay it after EMVOption check * Remove winscard lib from windows dependencies * Properly displaying errors * Adding a dot in Language.xml * Catching TLVException * Removing unused code * Remove unusefull comments * Trying to fix 0x1f error * Update IccDataExtractor.cpp * Delete History.xml * Fix get data without get pan * Cleanup code * changes for linux compilation but linking not working * error handling for linux * erasing emv data * Burn PAN * Burn PAN from memory * Uncomment selfcheck before merging master * burn corrected * EMV errors handling for Linux * EMV working for Linux CLI * Doc : Winscard Linux package and VeraCrypt versions --------- Co-authored-by: doriandu45 Co-authored-by: red4game Co-authored-by: Brice.Namy Co-authored-by: vocthor Co-authored-by: vocthor <67202139+vocthor@users.noreply.github.com> Co-authored-by: Andrei COCAN Co-authored-by: AndreiCocan <95496161+AndreiCocan@users.noreply.github.com> Co-authored-by: francoisLEROUX --- doc/html/Documentation.html | 1 + doc/html/EMV Smart Cards.html | 87 +++++++++++ doc/html/Keyfiles in VeraCrypt.html | 19 +++ doc/html/Keyfiles.html | 295 ++++++++++++++++++++++++++---------- 4 files changed, 325 insertions(+), 77 deletions(-) create mode 100644 doc/html/EMV Smart Cards.html (limited to 'doc') diff --git a/doc/html/Documentation.html b/doc/html/Documentation.html index f6a46629..e18feb35 100644 --- a/doc/html/Documentation.html +++ b/doc/html/Documentation.html @@ -66,6 +66,7 @@
  • Hot keys
  • Keyfiles
  • Security Tokens & Smart Cards +
  • EMV Smart Cards
  • Portable Mode
  • TrueCrypt Support
  • Converting TrueCrypt Volumes & Partitions diff --git a/doc/html/EMV Smart Cards.html b/doc/html/EMV Smart Cards.html new file mode 100644 index 00000000..d9c8716a --- /dev/null +++ b/doc/html/EMV Smart Cards.html @@ -0,0 +1,87 @@ + + + + + + VeraCrypt - Free Open source disk encryption with strong security for the + Paranoid + + + + + + +
    + VeraCrypt +
    + + + + + +
    +

    EMV Smart Cards

    +
    +

    + Windows and Linux versions of VeraCrypt offer to use EMV compliant + smart cards as a feature. Indeed, the use of PKCS#11 compliant smart + cards is dedicated to users with more or less cybersecurity skills. + However, in some situations, having such a card strongly reduces the + plausible deniability of the user. +

    +

    + To overcome this problem, the idea is to allow the use of a type of + smart card owned by anyone: EMV compliant smart cards. According to + the standard of the same name, these cards spread all over the world + are used to carry out banking operations. Using internal data of the + user's EMV card as keyfiles will strengthen the security of his volume + while keeping his denial plausible. +

    +

    + For more technical information, please see the section + EMV Smart Cards in the chapter + + Keyfiles. +

    +
    +
    + + diff --git a/doc/html/Keyfiles in VeraCrypt.html b/doc/html/Keyfiles in VeraCrypt.html index ed940d53..eea6939a 100644 --- a/doc/html/Keyfiles in VeraCrypt.html +++ b/doc/html/Keyfiles in VeraCrypt.html @@ -114,6 +114,25 @@ To close all opened security token sessions, either select Close All Security Token Sessions or define and use a hotkey combination (Settings > Hot Keys > Close All Security Token Sessions).

     

    +

    +EMV Smart Cards

    +
    +Windows and Linux versions of VeraCrypt can use directly as keyfiles data extracted from EMV compliant smart cards, supporting Visa, Mastecard or Maestro applications. As with PKCS-11 compliant smart cards, to use such data as VeraCrypt keyfiles, +click Add Token Files (in the keyfile dialog window). The last four digits of the card's Primary Account Number will be displayed, allowing the selection of the card as a keyfile source. +
    +The data extracted and concatenated into a single keyfile are as follow : ICC Public Key Certificate, Issuer Public Key Certificate and Card Production Life +Cycle (CPLC) data. They are respectively identified by the tags '9F46', '90' and '9F7F' in the card's data management system. These two certificates are specific to an application deployed on the EMV card and used for the Dynamic Data Authentication of the card +during banking transactions. CPLC data are specific to the card and not to any of its applications. They contain information on the production process of the smart card. Therefore both certificates and data are unique and static on any EMV compliant smart card.
    +
    +According to the ISO/IEC 7816 standard on which the EMV standard is based, communication with an EMV smart card is done through structured commands called APDUs, allowing to extract the data from the smart card. These data are encoded in the BER-TLV format, +defined by the ASN.1 standard, and therefore need to be parsed before being concatenated into a keyfile. No PIN is required to access and retrieve data from the card. To cope with the diversity of smart cards readers on the market, librairies compliant with the Microsoft Personal +Computer/Smart Card communication standard are used. The Winscard library is used. Natively available on Windows in System32, it then doesn't require any installation on this operating system. However, the libpcsclite1 package has to be installed on Linux.
    +
    +Since the card is read-only, it is not possible to import or delete data. However, data used as keyfiles can be exported locally in any binary file. During the entire cryptographic process of mounting or creating a volume, the certificates and CPLC data are never stored anywhere +other than in the user's machine RAM. Once the process is complete, these RAM memory areas are rigorously erased.
    +
    +It important to note that this feature is optional and disabled by default. It can be enabled in the Security Token Preferences parameters by checking the box provided.
    +

     

    Keyfile Search Path

    diff --git a/doc/html/Keyfiles.html b/doc/html/Keyfiles.html index db4fb52c..04dd3463 100644 --- a/doc/html/Keyfiles.html +++ b/doc/html/Keyfiles.html @@ -1,81 +1,222 @@ - + - - -VeraCrypt - Free Open source disk encryption with strong security for the Paranoid - - - - - + + + + VeraCrypt - Free Open source disk encryption with strong security for the + Paranoid + + + + + + +
    + VeraCrypt +
    -
    -VeraCrypt -
    + - + - - -
    -

    Keyfiles

    -
    -

    VeraCrypt keyfile is a file whose content is combined with a password. The user can use any kind of file as a VeraCrypt keyfile. The user can also generate a keyfile using the built-in keyfile generator, which utilizes the VeraCrypt RNG to generate a file - with random content (for more information, see the section -Random Number Generator).

    -

    The maximum size of a keyfile is not limited; however, only its first 1,048,576 bytes (1 MiB) are processed (all remaining bytes are ignored due to performance issues connected with processing extremely large files). The user can supply one or more keyfiles - (the number of keyfiles is not limited).

    -

    Keyfiles can be stored on PKCS-11-compliant [23] security tokens and smart cards protected by multiple PIN codes (which can be entered either using a hardware PIN pad or via the VeraCrypt GUI).

    -

    Keyfiles are processed and applied to a password using the following method:

    -
      -
    1. Let P be a VeraCrypt volume password supplied by user (may be empty) -
    2. Let KP be the keyfile pool
    3. Let kpl be the size of the keyfile pool KP, in bytes (64, i.e., 512 bits); -

      kpl must be a multiple of the output size of a hash function H

      -
    4. Let pl be the length of the password P, in bytes (in the current version: 0 ≤ -pl ≤ 64)
    5. if kpl > pl, append (kpl – pl) zero bytes to the password -P (thus pl = kpl)
    6. Fill the keyfile pool KP with kpl zero bytes.
    7. For each keyfile perform the following steps: -
        -
      1. Set the position of the keyfile pool cursor to the beginning of the pool
      2. Initialize the hash function H
      3. Load all bytes of the keyfile one by one, and for each loaded byte perform the following steps: -
          -
        1. Hash the loaded byte using the hash function H without initializing the hash, to obtain an intermediate hash (state) -M. Do not finalize the hash (the state is retained for next round).
        2. Divide the state M into individual bytes.
          -For example, if the hash output size is 4 bytes, (T0 || T1 || -T2 || T3) = M
        3. Write these bytes (obtained in step 7.c.ii) individually to the keyfile pool with the modulo 28 addition operation (not by replacing the old values in the pool) at the position of the pool cursor. After a byte is written, the pool cursor position - is advanced by one byte. When the cursor reaches the end of the pool, its position is set to the beginning of the pool. -
        -
      -
    8. Apply the content of the keyfile pool to the password P using the following method: -
        -
      1. Divide the password P into individual bytes B0...Bpl-1.
        -Note that if the password was shorter than the keyfile pool, then the password was padded with zero bytes to the length of the pool in Step 5 (hence, at this point the length of the password is always greater than or equal to the length of the keyfile pool). -
      2. Divide the keyfile pool KP into individual bytes G0...Gkpl-1 -
      3. For 0 ≤ i < kpl perform: Bi = Bi ⊕ Gi
      4. P = B0 || B1 || ... || Bpl-2 || -Bpl-1
      -
    9. The password P (after the keyfile pool content has been applied to it) is now passed to the header key derivation function PBKDF2 (PKCS #5 v2), which processes it (along with salt and other data) using a cryptographically secure hash algorithm - selected by the user (e.g., SHA-512). See the section -Header Key Derivation, Salt, and Iteration Count for more information. -
    -

    The role of the hash function H is merely to perform diffusion [2]. CRC-32 is used as the hash function -H. Note that the output of CRC-32 is subsequently processed using a cryptographically secure hash algorithm: The keyfile pool content (in addition to being hashed using CRC-32) is applied to the password, which is then passed to the header key derivation - function PBKDF2 (PKCS #5 v2), which processes it (along with salt and other data) using a cryptographically secure hash algorithm selected by the user (e.g., SHA-512). The resultant values are used to form the header key and the secondary header key (XTS mode).

    -

     

    -

    Next Section >>

    -
    -
    +
    +

    Keyfiles

    +
    +

    + VeraCrypt keyfile is a file whose content is combined with a password. + The user can use any kind of file as a VeraCrypt keyfile. The user can + also generate a keyfile using the built-in keyfile generator, which + utilizes the VeraCrypt RNG to generate a file with random content (for + more information, see the section + + Random Number Generator). +

    +

    + The maximum size of a keyfile is not limited; however, only its first + 1,048,576 bytes (1 MiB) are processed (all remaining bytes are ignored + due to performance issues connected with processing extremely large + files). The user can supply one or more keyfiles (the number of + keyfiles is not limited). +

    +

    + Keyfiles can be stored on PKCS-11-compliant [23] security tokens and + smart cards protected by multiple PIN codes (which can be entered + either using a hardware PIN pad or via the VeraCrypt GUI). +

    +

    + EMV-compliant smart cards' data can be used as keyfile, see chapter + + EMV Smart Cards. +

    +

    + Keyfiles are processed and applied to a password using the following + method: +

    +
      +
    1. + Let P be a VeraCrypt volume password supplied by user (may + be empty) +
      2. +
    2. Let KP be the keyfile pool
      3. +
    3. + Let kpl be the size of the keyfile pool KP, in + bytes (64, i.e., 512 bits); +

      + kpl must be a multiple of the output size of a hash function H +

      +
      4. +
    4. + Let pl be the length of the password P, in bytes + (in the current version: 0 ≤ pl ≤ 64) +
      5. +
    5. + if kpl > pl, append (kpl – pl) zero bytes + to the password P (thus pl = kpl) +
      6. +
    6. + Fill the keyfile pool KP with kpl zero bytes. +
      7. +
    7. + For each keyfile perform the following steps: +
        +
      1. + Set the position of the keyfile pool cursor to the beginning of + the pool +
        2. +
      2. Initialize the hash function H
        3. +
      3. + Load all bytes of the keyfile one by one, and for each loaded + byte perform the following steps: +
          +
        1. + Hash the loaded byte using the hash function + H without initializing the hash, to obtain an + intermediate hash (state) M. Do not finalize the + hash (the state is retained for next round). +
          2. +
        2. + Divide the state M into individual bytes.
          + For example, if the hash output size is 4 bytes, (T0 || T1 || T2 || T3) = M +
          3. +
        3. + Write these bytes (obtained in step 7.c.ii) individually to + the keyfile pool with the modulo 28 addition + operation (not by replacing the old values in the pool) at + the position of the pool cursor. After a byte is written, + the pool cursor position is advanced by one byte. When the + cursor reaches the end of the pool, its position is set to + the beginning of the pool. +
          4. +
        +
        4. +
      +
      8. +
    8. + Apply the content of the keyfile pool to the password + P using the following method: +
        +
      1. + Divide the password P into individual bytes B0...Bpl-1.
        + Note that if the password was shorter than the keyfile pool, + then the password was padded with zero bytes to the length of + the pool in Step 5 (hence, at this point the length of the + password is always greater than or equal to the length of the + keyfile pool). +
        2. +
      2. + Divide the keyfile pool KP into individual bytes + G0...Gkpl-1 +
        3. +
      3. For 0 ≤ i < kpl perform: Bi = Bi ⊕ Gi
        4. +
      4. + P = B0 || B1 || + ... || Bpl-2 || Bpl-1 +
        5. +
      +
      9. +
    9. + The password P (after the keyfile pool content has been + applied to it) is now passed to the header key derivation function + PBKDF2 (PKCS #5 v2), which processes it (along with salt and other + data) using a cryptographically secure hash algorithm selected by + the user (e.g., SHA-512). See the section + + Header Key Derivation, Salt, and Iteration Count + for more information. +
      10. +
    +

    + The role of the hash function H is merely to perform + diffusion [2]. CRC-32 is used as the hash function H. Note + that the output of CRC-32 is subsequently processed using a + cryptographically secure hash algorithm: The keyfile pool content (in + addition to being hashed using CRC-32) is applied to the password, + which is then passed to the header key derivation function PBKDF2 + (PKCS #5 v2), which processes it (along with salt and other data) + using a cryptographically secure hash algorithm selected by the user + (e.g., SHA-512). The resultant values are used to form the header key + and the secondary header key (XTS mode). +

    +

     

    +

    + Next Section >> +

    +
    +
    +
    + + -- cgit v1.2.3