topic Re: test vectors for SCC (security controller) in non-secure mode in i.MX Processors

test vectors for SCC (security controller) in non-secure mode

martinkaiser — Thu, 26 Feb 2015 15:48:38 GMT

Dear all,

I'm looking at the SCC in an i.MX258 chipset. For now, I'm using non-secure mode (preferably in 3DES).

Do you have any test vectors (input data, iv for 3des and corresponding output data) that I could use to verify my calculations?

Best regards,

Martin

Re: test vectors for SCC (security controller) in non-secure mode

Yuri — Fri, 27 Feb 2015 03:04:04 GMT

Triple-DES tests are described in NIST Special Publication :
“Modes of Operation Validation System for the Triple Data Encryption
Algorithm (TMOVS): Requirements and Procedures”.
An additional test, the Multi-block Message Text (MMT), is also required.

http://csrc.nist.gov/publications/nistpubs/800-20/800-20.pdf

http://csrc.nist.gov/groups/STM/cavp/

Also, let me remind, for i.MX25 "in non-secure mode [...] the decryption engine is available
for test purposes only with a default 168-bit 3DES ...".

Have a great day,
Yuri.

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

Re: test vectors for SCC (security controller) in non-secure mode

igorpadykov — Fri, 27 Feb 2015 04:35:15 GMT

Hi Martin

in general i.MX25 SCC tests are described in pdk2009_12_imx25_Linux_RM.pdf

Chapter 19 Security Drivers IMX25_0912_SDK_LINUXDOCS_BUNDLE

code examples in ltib (L2.6.31_09.12.00_SDK_SOURCE) imx-test package :

imx-test-09.12.00/module_test/scc_test_driver.c

Best regards

igor

Re: test vectors for SCC (security controller) in non-secure mode

martinkaiser — Fri, 27 Feb 2015 09:00:48 GMT

Hi Igor and Yuri,

thanks for your responses.

Actually, I was looking for samples of input data and corresponding output data for the published test key. My hope was that I could then do the exact same calculation with OpenSSL and get a better idea how the 3des engine works internally.

I managed to get this to work meanwhile so the issue is solved for me.

Regards,

Martin