Joomla! Joomla!

In this section you can find developed Test Vector Response Files used to verify the implementations of DiceLock 9.0.0.1 for Windows and Linux.

Test Vectors posted in this section address the use of DiceLockXTSDigested class, which makes use of XTS_Mode (XEX-based tweaked-codebook mode with ciphertext stealing XTS block cipher operation mode algorithm), when randomness evaluation and reciphering is performed over full ciphertext (ciphered plaintext plus ciphered hash digest of all plaintext).

DiceLockXTSDigested class can be employed with any of AES 128, AES 192, AES 256, Camellia 128, Camellia 192, Camellia 256, Serpent 128, Serpent 192, Serpent 256, Twofish 128, Twofish 192 or Twofish 256 block ciphers.

These are DiceLock cipher architecture test vector input data files for:
CheckDiceLockXTSDigestedFull for Windows Windows program to verify DiceLock cipher implementation when DiceLockXTSDigested class, which uses XTS_Mode, is applied to full plaintext as a whole.
CheckDiceLockXTSDigestedFull-x for Linux Linux program to verify DiceLock cipher implementation when DiceLockXTSDigested class, which uses XTS_Mode, is applied to full plaintext as a whole.



DiceLock cipher architecture input response test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x can be downloaded from different sources:

CheckDiceLockXTSDigestedFull-9.0.0.1-ResponseTests.zip Full package file download with all response input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x.

DiceLockXTSDigested applied to full text making use of AES 128 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with AES 128 (Advanced Encryption Standard), 128 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of AES 192 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with AES 192 (Advanced Encryption Standard), 192 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of AES 256 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with AES 256 (Advanced Encryption Standard), 256 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Camellia 128 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Camellia 128, 128 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Camellia 192 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Camellia 192, 192 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Camellia 256 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Camellia 256, 256 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Serpent 128 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Serpent 128, 128 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Serpent 192 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Serpent 192, 192 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Serpent 256 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Serpent 256, 256 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Twofish 128 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Twofish 128, 128 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Twofish 192 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Twofish 192, 192 bit symmetric key block cipher, and applied to full plaintext as a whole.
DiceLockXTSDigested applied to full text making use of Twofish 256 Input test vector files for CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x when DiceLockXTSDigested class is used with Twofish 256, 256 bit symmetric key block cipher, and applied to full plaintext as a whole.

CheckDiceLockXTSDigestedFull for Windows and CheckDiceLockXTSDigestedFull-x for Linux make use of indicated response test vector files that must be included in './ResponseTests' folder and will generate corresponding output vector test files in './OutputTests' folder.

In order to clarify which options within CheckDiceLockXTSDigestedFull and CheckDiceLockXTSDigestedFull-x programs can be executed, the input test vector files that are going to be processed and the ouput test vector files that will be produced follow a logical notation.

Online guides clarifying input and output test vector file naming notation, their content and how to check verification are:
Response test vector file naming Input test vector file naming convention and clarification of content tests to be processed.
Output test vector file naming Output test vector file naming convention, clarification of content and how to check correctness of verification that will be produced.

 

In Output test vector file naming page alongside with name convention and content clarification there is a guide to easily verify correctness of test performed.