-
-
Notifications
You must be signed in to change notification settings - Fork 221
Is there a mode for differential restart? #1073
Replies: 2 comments · 15 replies
-
If you restart the same scan with the same firmware and the same log directory you should get a note like the following: this gives you the possibility to try a restart. Warning: this feature is an experimental feature but should work not to bad in most cases |
Beta Was this translation helpful? Give feedback.
All reactions
-
have you done a clean installation with "sudo ./installer.sh -d"? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Also -- this is a fresh clone of the latest release |
Beta Was this translation helpful? Give feedback.
All reactions
-
ok, the base image looks good. I do not understand how you got the failed checks from #1073 (reply in thread) Is a dependency check working? Is a typical EMBA scan on a random firmware working? What are your starting parameters? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Did a fresh install -- but running with the -i switch still comes up with that same issue EMBA scan works all good if I use the -y switch, i.e. remove the old log dir -- otherwise -i switch fails with dependency checks Here is the dependency check results of
|
Beta Was this translation helpful? Give feedback.
All reactions
-
har ... I got your problem. The help is regarding -i is wrong:
-i is only EMBA internally used and I will remove it from the help (or add a comment) |
Beta Was this translation helpful? Give feedback.
All reactions
-
ok, I did another test and something is broken in here. I will take a deeper look at this issue. |
Beta Was this translation helpful? Give feedback.
All reactions
-
see #1077 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Please check PR #1078 |
Beta Was this translation helpful? Give feedback.
All reactions
-
Would a “restart” allow for the specification of a new scan profile? |
Beta Was this translation helpful? Give feedback.
All reactions
-
Sorry but this would not work. The restart mechanism is only checking if a module was already finished without further tests. As some modules have different behavior in the different scanning modes this restart scan will not re-run modules with different behavior as they are already finished. In theory you probably could try tweaking your emba.log to run the needed modules but I would not recommend doing so., So, if you need more details after a quick scan you need to startup again with a default or full scan. |
Beta Was this translation helpful? Give feedback.
-
Basically, is there a switch to ignore modules that have already successfully completed in past cycles on the same firmware?
As such, it may be worth doing a diff on the firmware at start to verify it has not changed.
Otherwise analysis would probably need to start from scratch anyways.
Did not find any directives in the help menu, hence asking :)
Beta Was this translation helpful? Give feedback.
All reactions