Common Tool Information - Revision history

Adriel: /* Class Diagram */

2016-09-29T03:25:16Z

‎Class Diagram

Adriel at 18:23, 14 July 2016

2016-07-14T18:23:32Z

Adriel: /* Using the Analyzer */

2016-07-14T18:22:06Z

‎Using the Analyzer

Adriel at 18:05, 14 July 2016

2016-07-14T18:05:31Z

Adriel: /* Class Diagram */

2016-07-14T17:28:58Z

‎Class Diagram

Adriel: /* Class Diagram */

2016-07-14T17:28:22Z

‎Class Diagram

Adriel: /* Class Diagram */

2016-07-14T17:27:54Z

‎Class Diagram

Adriel: /* Class Diagram */

2016-07-14T17:11:17Z

‎Class Diagram

Adriel: /* Class Diagram */

2016-07-14T17:09:11Z

‎Class Diagram

Adriel: /* Class Diagram */

2016-07-14T17:07:36Z

‎Class Diagram

@@ Line 10: / Line 10: @@
 [[File:Cw classdiagram.png|1100x1100px]]
-The general architectural idea is to start the Flow with a TraceSource, allow the connection of multiple preprocessing modules (that are both: ActiveTraceObserver and TraceSource) and end the chain in an TraceObserver (that can be a widget or an AnalysisSource). The sigTracesChanged signal (in the TraceSource objects) is used to propagate this notification through the chain and activate a callback method (processTraces) in the ActiveTraceObserver objects (like the WaveFormWidget) to read the new data. The PassiveTraceObservers (like the AnalysisSource and the TraceRecorder widget) will ignore this signal, so the processSignal() should be called manually.
+The general architectural idea is to start the Flow with a TraceSource, allow the connection of multiple preprocessing modules (that are both: ActiveTraceObserver and TraceSource) and end the chain in a TraceObserver (that can be a widget or an AnalysisSource). The sigTracesChanged signal (in the TraceSource objects) is used to propagate this notification through the chain and activate a callback method (processTraces) in the ActiveTraceObserver objects (like the WaveFormWidget) to read the new data. The PassiveTraceObservers (like the AnalysisSource and the TraceRecorder widget) will ignore this signal, so the processSignal() should be called manually.
 In the diagram bellow, the arrows show the data flow (the requests are made in the opposite direction) and the vertical lines the inheritance structure:

@@ Line 5: / Line 5: @@
 == Loading/Saving the Settings ==
-The settings are not saved with the project (we may improve it in the future), but instead, you can use the "Save Settings" option (inside the Project menu) to dump this information to the "settings.cwset" file, inside the project directory. Once saved, the settings can be re-loaded using the load button in the settings tabs (general, scope, traget,...). Another possibility would be to use the Save Button and choose different filenames for each settings profile that you wanto to use.
+The settings are not saved with the project (we may improve it in the future), but instead, you can use the "Save Settings" option (inside the Project menu) to dump this information to the "settings.cwset" file, inside the project directory. Once saved, the settings can be re-loaded using the load button in the settings tabs (general, scope, traget,...). Another possibility would be to use the Save Button and choose different filenames for each settings profile that you want to use.
-−
-== 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.
-−
-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 "Trace Explorer" tab enables a set of helper scripts needed by some of the analysis algorithms (like the POI detection in the Template attack).
 == Class Diagram ==

@@ Line 9: / Line 9: @@
 == 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.
 == Class Diagram ==

@@ Line 6: / Line 6: @@
 == Loading/Saving the Settings ==
 The settings are not saved with the project (we may improve it in the future), but instead, you can use the "Save Settings" option (inside the Project menu) to dump this information to the "settings.cwset" file, inside the project directory. Once saved, the settings can be re-loaded using the load button in the settings tabs (general, scope, traget,...). Another possibility would be to use the Save Button and choose different filenames for each settings profile that you wanto to use.
 == Class Diagram ==

← Older revision		Revision as of 17:28, 14 July 2016
Line 34:		Line 34:
	AutoScript - helper class with methods to setup the output when the class that uses it need to have scripts as output.		AutoScript - helper class with methods to setup the output when the class that uses it need to have scripts as output.

−	Parameterized - helper class with methods maintain (add/find/delete) parameters when the class that extends it makes use of parameters.	+	Parameterized - helper class with methods to maintain (add/find/delete) the parameters when the class that extends it makes use of parameters.

@@ Line 22: / Line 22: @@
                                      ...                                                       Template                     ...
-Description of some important classes:
+Description of some other important classes:
 AnalysisSource - define signals (started, updated and done) that the AnalysisObserver objects will "listen" when emitted by these objects to execute the appropriate operation.

← Older revision		Revision as of 17:11, 14 July 2016
Line 23:		Line 23:

	The AnalysisSource defines signals (started, updated and done) that the AnalysisObserver objects will "listen" when emitted by these objects to execute the appropriate operation.		The AnalysisSource defines signals (started, updated and done) that the AnalysisObserver objects will "listen" when emitted by these objects to execute the appropriate operation.
		+	The AttackObserver is a specialized class that will listen to AttackBaseClass signals and update the ResultWidgets (table, plots,...)

@@ Line 14: / Line 14: @@
 In the diagram bellow, the arrows show the data flow (the requests are made in the opposite direction) and the vertical lines the inheritance structure:
-   TraceSource -> [ActiveTraceObserver, TraceSource] -> [ActiveTraceObserver/PassiveTraceObserver]   AnalysisSource -> AnalysisObserver
+   TraceSource -> [ActiveTraceObserver, TraceSource] -> [ActiveTraceObserver/PassiveTraceObserver]  AnalysisSource -> AnalysisObserver
-         |                          |     /                  |                 |        \              /                         |
+         |                          |     /                  |                    |        \             /                   |
-      Channel                 PreprocessingBase              |                    |      AttackBaseClass               AttackObserver
+      Channel                 PreprocessingBase              |                    |        AttackBaseClass             AttackObserver
-    TraceManager                      |                WaveFormWidget             |              |                            |
+    TraceManager                      |                WaveFormWidget             |               |                          |
-                                  ResyncSAD                             TraceRecorder            |                       ResultsTable
+                                  ResyncSAD                                 TraceRecorder         |                     ResultsTable
-                                AddNoiseJitter                                                  CPA                   CorrelationVsTrace
+                                AddNoiseJitter                                                   CPA                 CorrelationVsTrace
-                                     ...                                                      Template                       ...
+                                     ...                                                       Template                     ...
 The AnalysisSource defines signals (started, updated and done) that the AnalysisObserver objects will "listen" when emitted by these objects to execute the appropriate operation.