You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Inconsistent directory labeling for "ssh_scan" #180
The directory ssh_scan is inconsistently using an underscore instead of a minus in comparison to other scanners (test-scan, kube-hunter), leading to a necessary workaround in the install script.
In general, ssh_scan is used as a path at the moment, whereas ssh-scan is used in the scantype and the tests.
We've tried to use that name as much as possible. Some names (e.g. kubernetes and Helm names) don't allow underscores. That's why we've changed it there.
So when lot of tools do not allow underscores, why do we name it with underscore and add workarounds? The reason that the original name is with underscore is IMHO not a good reason. We can name it as we like. Eg. if the scanner is named ssh$scan we would rename it anyway because such.
So from architecture I strongly recommend renaming the directory althoug the scanner has _ in its original name.
Activity
J12934 commentedon Oct 23, 2020
It's written using an underscore as that is the official name of the tool https://github.com/mozilla/ssh_scan.
We've tried to use that name as much as possible. Some names (e.g. kubernetes and Helm names) don't allow underscores. That's why we've changed it there.
nigthknight commentedon Oct 26, 2020
I guess we can close this issue
Weltraumschaf commentedon Oct 26, 2020
So when lot of tools do not allow underscores, why do we name it with underscore and add workarounds? The reason that the original name is with underscore is IMHO not a good reason. We can name it as we like. Eg. if the scanner is named ssh$scan we would rename it anyway because such.
So from architecture I strongly recommend renaming the directory althoug the scanner has _ in its original name.
#180 Added "Schedule" print column to ScheduledScan CRD
#180 Regenerated CRD yaml files
#180 Fix to generated scheduledScan yaml file
#180 Added "Schedule" print column to ScheduledScan CRD
#180 Regenerated CRD yaml files
#180 Fix to generated scheduledScan yaml file
#180 Added "Schedule" print column to ScheduledScan CRD
#180 Regenerated CRD yaml files
#180 Fix to generated scheduledScan yaml file
#180 Added "Schedule" print column to ScheduledScan CRD
#180 Regenerated CRD yaml files
#180 Fix to generated scheduledScan yaml file
#180 Added "Schedule" print column to ScheduledScan CRD
#180 Regenerated CRD yaml files
#180 Fix to generated scheduledScan yaml file
#180 Added "Schedule" print column to ScheduledScan CRD
#180 Regenerated CRD yaml files
#180 Fix to generated scheduledScan yaml file