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
When Drill Debian package is installed, the reported source package name is https://github.com/yatima1460/Drill. A URL is not a valid package name. This is a problem for tools that need a real package name to work properly.
For example, debsecan (a classic tool used to scan for vulnerabilities on Debian installations) cannot work anymore due to this anomaly:
So, when Drill is installed, the result is that the overall system cannot be analyzed for security vulnerabilities...
Remark: I agree that debsecan should not fail like that. It should report the anomaly, discard Drill from the analysis and continue his work. But all tools that expects for a valid package name are potentially affected by this small mistake.
For information, the Debian package naming rules are (from Debian policy):
Package names (both source and binary, see Package) must consist only of lower case letters (a-z), digits (0-9), plus (+) and minus (-) signs, and periods (.). They must be at least two characters long and must start with an alphanumeric character.
Environment:
Installation: Debian package
Version: v566
OS: Ubuntu 20.10
The text was updated successfully, but these errors were encountered:
When Drill Debian package is installed, the reported source package name is
https://github.com/yatima1460/Drill
. A URL is not a valid package name. This is a problem for tools that need a real package name to work properly.For example, debsecan (a classic tool used to scan for vulnerabilities on Debian installations) cannot work anymore due to this anomaly:
So, when Drill is installed, the result is that the overall system cannot be analyzed for security vulnerabilities...
Remark: I agree that
debsecan
should not fail like that. It should report the anomaly, discard Drill from the analysis and continue his work. But all tools that expects for a valid package name are potentially affected by this small mistake.For information, the Debian package naming rules are (from Debian policy):
Environment:
The text was updated successfully, but these errors were encountered: