-
Notifications
You must be signed in to change notification settings - Fork 179
Closed
Labels
bugBugsBugs
Description
🐞 Bug report
Describe the bug
SCB on currently latest release v4.01 is unable to run amass scans due to the following reasons:
- Amass v4.x has breaking changes (See Upgrade amass to v4.x #1833) so upgrading was not quickly possible.
- Amass deletes periodically (~monthly) their docker images. This means that the version v3.23.2 that is included in SCB v4.0.1 is no longer available. Only v3.x version that is still available in DockerHub is v3.23.2
- Amass v3.23.2 Docker image currently has an issue where the container does not exit correctly, resulting into the scan never reaching the
FinishedState. See Docker container not stopping owasp-amass/amass#918
A notice has been added here: #1848
Steps To Reproduce
Run an amass scan
Expected behavior
- An Amass scan should run correctly.
- Notice Added a notice in documentation that amass is currently not functional #1848 should be removed
System (please complete the following information):
- secureCodeBox Version/Release: v4.0.1
Screenshots / Logs
Additional context
Metadata
Metadata
Assignees
Labels
bugBugsBugs
Type
Projects
Status
Done