CW-Analyzer Tool - Revision history

Adewar at 13:32, 24 August 2023

2023-08-24T13:32:40Z

Adriel at 21:46, 15 July 2016

2016-07-15T21:46:20Z

Adriel: /* Sum of Difference */

2016-07-15T17:02:32Z

‎Sum of Difference

Adriel: /* Using the Analyzer */

2016-07-14T20:48:44Z

‎Using the Analyzer

Adriel at 20:46, 14 July 2016

2016-07-14T20:46:47Z

Adriel at 20:43, 14 July 2016

2016-07-14T20:43:36Z

Adriel at 20:41, 14 July 2016

2016-07-14T20:41:21Z

Adriel at 20:31, 14 July 2016

2016-07-14T20:31:23Z

Adriel: /* Using the Analyzer */

2016-07-14T18:29:25Z

‎Using the Analyzer

Adriel: /* Using the Analyzer */

2016-07-14T18:24:26Z

‎Using the Analyzer

← Older revision		Revision as of 13:32, 24 August 2023
Line 1:		Line 1:
		+	'''WARNING: THE CHIPWHISPERER CAPTURE AND ANALYZER TOOLS ARE DEPRECATED. AS SUCH, WE ARE UNABLE TO PROVIDE SUPPORT FOR THESE TOOLS OR RELEASES THAT INCLUDE THESE TOOLS.'''
		+
	The objective of this tool is to analyze the traces captured from a given scope.		The objective of this tool is to analyze the traces captured from a given scope.

@@ Line 2: / Line 2: @@
 Main features:
-* CPA and Profiling attack;
+* CPA and Profiling types of attack;
 * Built-in preprocessing modules (decimation, resync, digital filter, normalize and noise);
 * Record preprocessed traces output;
@@ Line 12: / Line 12: @@
 == Using the Analyzer ==
-After loading the project, you will need to setup the analysis environment. In the analyzer, the settings tabs are used to automatically generate the analysis script (shown in the "Analysis Script" dock) that is executed when the attack is started. This way, the user can manually edit the code having even more flexibility. This code can also be saved and loaded both through the console (python filename) or the GUI. You can also copy this file to the analyzer/scripts folder so it will appear in the Project->Example Scripts menus in the next time you execute the tool.
+After loading the project, you will need to setup the analysis environment first.
-In the "Analysis Script" dock, the constructor is called automatically every time a new script is generated. It is done because widgets like the waveform viewer should update the trace output of the preprocessing modules when the user modify its settings. The run() method is executed when the "Start Analysis" button in the toolbar is pressed. Custom methods can be executed by selecting it in the code and right clicking: a "Run Function" option will show up.
+In the analyzer, the settings tabs are used to automatically generate the analysis script (shown in the "Analysis Script" dock). This code can be edited by the user for a more "advanced" usage. It can also be saved and loaded through:
 The "Attack Script Generator" is the main settings tab. It allows the user to set the Preprocessing modules that should be applied over the original traces and the Attack module. The Preprocessing and the Attack tabs will update accordingly.

@@ Line 55: / Line 55: @@
 Deal with resampling 'bins' based on zero-crossing detection.
-=== Sum of Difference ===
+=== Resync: Sum-of-Difference ===
 Minimize the 'Sum of Absolute Difference' (SAD), also known as 'Sum of Absolute Error'. Uses a portion of one of the traces as the 'reference'. This reference is then slid over the 'input window' for each trace, and the amount of shift resulting in the minimum SAD criteria is selected as the shift amount for that trace.
 See [[Sum of Absolute Difference (SAD) Pre-Processing]] for more information.

@@ Line 14: / Line 14: @@
 After loading the project, you will need to setup the analysis environment. In the analyzer, the settings tabs are used to automatically generate the analysis script (shown in the "Analysis Script" dock) that is executed when the attack is started. This way, the user can manually edit the code having even more flexibility. This code can also be saved and loaded both through the console (python filename) or the GUI. You can also copy this file to the analyzer/scripts folder so it will appear in the Project->Example Scripts menus in the next time you execute the tool.
-In the "Analysis Script" dock, the constructor is called automatically every time a new script is generated. It is done because widgets like the waveform viewer should update the trace output of the preprocessing modules when the user modify its settings. The run() method is executed when the start analysis button is pressed. Custom methods can be executed by selecting it in the code and right clicking: a "Run Function" option will show up.
+In the "Analysis Script" dock, the constructor is called automatically every time a new script is generated. It is done because widgets like the waveform viewer should update the trace output of the preprocessing modules when the user modify its settings. The run() method is executed when the "Start Analysis" button in the toolbar is pressed. Custom methods can be executed by selecting it in the code and right clicking: a "Run Function" option will show up.
 The "Attack Script Generator" is the main settings tab. It allows the user to set the Preprocessing modules that should be applied over the original traces and the Attack module. The Preprocessing and the Attack tabs will update accordingly.

@@ Line 9: / Line 9: @@
 * Set of result widgets: Correlation vs Traces plot; Output vs Point plot; PGE vs Trace plot; PGE Table; Waveform Viewer.
-[[File:Screen Shot 2016-07-12 at 4.02.17 PM.png|400px]]
+[[File:Screen Shot 2016-07-12 at 4.02.17 PM.png|1100px]]
 == Using the Analyzer ==

← Older revision		Revision as of 20:31, 14 July 2016
Line 1:		Line 1:
		+	The objective of this tool is to analyze the traces captured from a given scope.
		+	Main features:
		+
	== Using the Analyzer ==		== Using the Analyzer ==
	After loading the project, you will need to setup the analysis environment. In the analyzer, the settings tabs are used to automatically generate the analysis script (shown in the "Analysis Script" dock) that is executed when the attack is started. This way, the user can manually edit the code having even more flexibility. This code can also be saved and loaded both through the console (python filename) or the GUI. You can also copy this file to the analyzer/scripts folder so it will appear in the Project->Example Scripts menus in the next time you execute the tool.		After loading the project, you will need to setup the analysis environment. In the analyzer, the settings tabs are used to automatically generate the analysis script (shown in the "Analysis Script" dock) that is executed when the attack is started. This way, the user can manually edit the code having even more flexibility. This code can also be saved and loaded both through the console (python filename) or the GUI. You can also copy this file to the analyzer/scripts folder so it will appear in the Project->Example Scripts menus in the next time you execute the tool.

@@ Line 4: / Line 4: @@
 In the "Analysis Script" dock, the constructor is called automatically every time a new script is generated. It is done because widgets like the waveform viewer should update the trace output of the preprocessing modules when the user modify its settings. The run() method is executed when the start analysis button is pressed. Custom methods can be executed by selecting it in the code and right clicking: a "Run Function" option will show up.
-The "Attack Script Generator" is the main settings tab. It allows the user to set the preprocessing modules that should be applied over the original traces and the Attack module. The Preprocessing and the Attack tabs will update accordingly.
+The "Attack Script Generator" is the main settings tab. It allows the user to set the Preprocessing modules that should be applied over the original traces and the Attack module. The Preprocessing and the Attack tabs will update accordingly.
 The "Trace Explorer" tab enables a set of helper scripts needed by some of the analysis algorithms (like the POI detection in the Template attack).

← Older revision		Revision as of 18:24, 14 July 2016
Line 7:		Line 7:

	The "Trace Explorer" tab enables a set of helper scripts needed by some of the analysis algorithms (like the POI detection in the Template attack).		The "Trace Explorer" tab enables a set of helper scripts needed by some of the analysis algorithms (like the POI detection in the Template attack).
−

	== Preprocessing Modules ==		== Preprocessing Modules ==