CryptoAuthentication SOIC Xplained Pro Starter Kit (DM320109) - Revision history

NKirnbauer: fixed link

2024-11-10T19:45:20Z

fixed link

← Older revision		Revision as of 19:45, 10 November 2024
Line 91:		Line 91:
	== Courses ==		== Courses ==

	* [[Ausgewählte ~~Artikel~~ der IT Security]] (2021)		* [[Ausgewählte Kapitel der IT-Security]] (2021)

	== References ==		== References ==

PFenzel at 18:48, 18 November 2021

2021-11-18T18:48:07Z

← Older revision		Revision as of 18:48, 18 November 2021
Line 1:		Line 1:
	== Summary ==		== Summary ==
	~~!!!! W O R K I N P R O G R E S S !!!!~~

	This documentation describes the usage of the CryptoAuthentication SOIC Xplained Pro Starter Kit (DM320109)		This documentation describes the usage of the CryptoAuthentication SOIC Xplained Pro Starter Kit (DM320109)
Line 74:		Line 73:

	* For an HMAC challenge use the command (A0) of the menu. This will perform an HMAC challenge against slot 3 and 12. Both are derived from the root key. This examples compares the HMAC digest generated on the client and an HMAC on the host using all possible modes (start mode / update mode / finalize mode).		* For an HMAC challenge use the command (A0) of the menu. This will perform an HMAC challenge against slot 3 and 12. Both are derived from the root key. This examples compares the HMAC digest generated on the client and an HMAC on the host using all possible modes (start mode / update mode / finalize mode).
			[[File:ATSHA204HMAC.png]]

			* ATSHA204a also supports key rolling to prevent repeated use of the same key value. After a certain number of uses of the current key value gets replaced with the SHA-256 digest of itself combined with some offset e.g. a constant, a serial number or model number. This is implemented by using the DeriveKey command. Selecting AE will perform a rolling key operation on key 4. Further details can be found in Philly's Tutorial.

PFenzel at 18:33, 18 November 2021

2021-11-18T18:33:10Z

← Older revision		Revision as of 18:33, 18 November 2021
Line 72:		Line 72:
	* If bit 6 is set to 1, then a slot which is secret allows encrypted read to access. Reading these slots returns the encrypted data which the host then has to decrypt by the read key defined in the slot configuration of the slot being read. Selecting command (A2) reads the encrypted slots as shown below:		* If bit 6 is set to 1, then a slot which is secret allows encrypted read to access. Reading these slots returns the encrypted data which the host then has to decrypt by the read key defined in the slot configuration of the slot being read. Selecting command (A2) reads the encrypted slots as shown below:
	[[File:ATSHA204EncryptRead.png]]		[[File:ATSHA204EncryptRead.png]]

			* For an HMAC challenge use the command (A0) of the menu. This will perform an HMAC challenge against slot 3 and 12. Both are derived from the root key. This examples compares the HMAC digest generated on the client and an HMAC on the host using all possible modes (start mode / update mode / finalize mode).


	~~=== Implementation for XXXX ===~~
	~~.... TO BE COMPLETED ....~~

PFenzel at 20:52, 14 November 2021

2021-11-14T20:52:17Z

← Older revision		Revision as of 20:52, 14 November 2021
Line 69:		Line 69:
	* To interpret the slot configuration as displayed above the overview below will give useful information. More details can be found in the ATSHA204A data sheet.		* To interpret the slot configuration as displayed above the overview below will give useful information. More details can be found in the ATSHA204A data sheet.
	[[File:ATSHA204ConfigurationZone.png]]		[[File:ATSHA204ConfigurationZone.png]]

			* If bit 6 is set to 1, then a slot which is secret allows encrypted read to access. Reading these slots returns the encrypted data which the host then has to decrypt by the read key defined in the slot configuration of the slot being read. Selecting command (A2) reads the encrypted slots as shown below:
			[[File:ATSHA204EncryptRead.png]]

PFenzel at 20:33, 14 November 2021

2021-11-14T20:33:46Z

← Older revision		Revision as of 20:33, 14 November 2021
Line 64:		Line 64:
	* Step 9 - validate key - command (AA)		* Step 9 - validate key - command (AA)

	* When selecting (02) you get the slot configuration which is saved in bytes 20 - 51 within the 88 bytes configuration zone		* When selecting (02) you get the slot configuration which is saved in bytes 20 - 51 within the 88 bytes configuration zone. There you have 16 slots of each 2 bytes containing the access restriction values for the slots in the data zone
	There you have 16 slots of each 2 bytes containing the access restriction values for the slots in the data zone
	[[File:ATSHA204SlotConfiguration.png]]		[[File:ATSHA204SlotConfiguration.png]]

	* To interpret the slot configuration as displayed above below ~~overview~~ will give useful information. More details can be found in the ATSHA204A data sheet.		* To interpret the slot configuration as displayed above the overview below will give useful information. More details can be found in the ATSHA204A data sheet.
	[[File:ATSHA204ConfigurationZone]]		[[File:ATSHA204ConfigurationZone.png]]

PFenzel at 20:27, 14 November 2021

2021-11-14T20:27:41Z

← Older revision		Revision as of 20:27, 14 November 2021
Line 51:		Line 51:
	* To get details like serial number about the device select (01). If your ATSHA204A is connected correctly, you should see similar information as follows:		* To get details like serial number about the device select (01). If your ATSHA204A is connected correctly, you should see similar information as follows:
	[[File:ATSHA204DeviceDetails.png]]		[[File:ATSHA204DeviceDetails.png]]


	* To configure the device, write all the keys to the slots and lock the device, you have to follow the below steps:		* To configure the device, write all the keys to the slots and lock the device, you have to follow the below steps:
	* Step 1 - configure the device - command (03) Personalize Device		* Step 1 - configure the device - command (03) Personalize Device
Line 63:		Line 65:

	* When selecting (02) you get the slot configuration which is saved in bytes 20 - 51 within the 88 bytes configuration zone		* When selecting (02) you get the slot configuration which is saved in bytes 20 - 51 within the 88 bytes configuration zone
	There you have 16 slots of each 2 bytes containing the access restriction values for the slots in the data zone		There you have 16 slots of each 2 bytes containing the access restriction values for the slots in the data zone
	[[File:ATSHA204SlotConfiguration.png]]		[[File:ATSHA204SlotConfiguration.png]]

			* To interpret the slot configuration as displayed above below overview will give useful information. More details can be found in the ATSHA204A data sheet.
			[[File:ATSHA204ConfigurationZone]]

PFenzel at 20:13, 14 November 2021

2021-11-14T20:13:05Z

← Older revision		Revision as of 20:13, 14 November 2021
Line 49:		Line 49:
	[[File:ATSHA204Menu.png]]		[[File:ATSHA204Menu.png]]
	* You can navigate through the different implementations via the menu		* You can navigate through the different implementations via the menu
	* To get details like serial number about the device select (01). If your ATSHA204A is connected correctly, you should see ~~informations~~ as follows:		* To get details like serial number about the device select (01). If your ATSHA204A is connected correctly, you should see similar information as follows:
	[[File:ATSHA204DeviceDetails.png]]		[[File:ATSHA204DeviceDetails.png]]
	* To configure the device, write all the keys to the slots and lock the device you have to follow the below steps:		* To configure the device, write all the keys to the slots and lock the device, you have to follow the below steps:
	* Step 1 - configure the device - command (03) Personalize Device		* Step 1 - configure the device - command (03) Personalize Device
	* Step 2 - lock the configuration zone - command (04)		* Step 2 - lock the configuration zone - command (04)
Line 61:		Line 61:
	* Step 8 - run deriveKey (Key Roll) for slot 4 - command (AE)		* Step 8 - run deriveKey (Key Roll) for slot 4 - command (AE)
	* Step 9 - validate key - command (AA)		* Step 9 - validate key - command (AA)

			* When selecting (02) you get the slot configuration which is saved in bytes 20 - 51 within the 88 bytes configuration zone
			There you have 16 slots of each 2 bytes containing the access restriction values for the slots in the data zone
			[[File:ATSHA204SlotConfiguration.png]]

PFenzel at 19:51, 14 November 2021

2021-11-14T19:51:52Z

@@ Line 49: / Line 49: @@
 [[File:ATSHA204Menu.png]]
 * You can navigate through the different implementations via the menu
 === Implementation for XXXX ===

PFenzel at 19:35, 14 November 2021

2021-11-14T19:35:09Z

← Older revision		Revision as of 19:35, 14 November 2021
Line 47:		Line 47:
	Flow control none		Flow control none
	* Press then the reset button on your DM320109 board and in the Tera Term terminal the menu of the program will appear		* Press then the reset button on your DM320109 board and in the Tera Term terminal the menu of the program will appear
			[[File:ATSHA204Menu.png]]
	* You can navigate through the different implementations via the menu		* You can navigate through the different implementations via the menu

PFenzel at 01:36, 3 November 2021

2021-11-03T01:36:10Z

← Older revision		Revision as of 01:36, 3 November 2021
Line 1:		Line 1:
	== Summary ==		== Summary ==
	!!!! W O R K I N P R O G R E S S !!!! ~~(Petra Fenzel)~~		!!!! W O R K I N P R O G R E S S !!!!

	This documentation describes the usage of the CryptoAuthentication SOIC Xplained Pro Starter Kit (DM320109)		This documentation describes the usage of the CryptoAuthentication SOIC Xplained Pro Starter Kit (DM320109)