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
If I run the current devel version I get the line "Command was: a perl script, too long to display" for every check, except umask. There it reads "Command was: umask".
I think the idea behind this in the 0.7 release was to provide additional background information on how the checks are performed. But something seems not to be working here. Many of the checks are in fact simple bash one-liners (such as find / -perm -4000 -type f to find suids) and should be displayed here. But they are not listed here, instead the annoying "Command was: a perl script, too long to display" is popping up.
I think in general providing details on how the tests are run is a great idea! But I think this should probably be a feature that is only part of the expert mode and might be too confusing for the default output.
The text was updated successfully, but these errors were encountered:
If I run the current devel version I get the line "Command was: a perl script, too long to display" for every check, except umask. There it reads "Command was: umask".
I think the idea behind this in the 0.7 release was to provide additional background information on how the checks are performed. But something seems not to be working here. Many of the checks are in fact simple bash one-liners (such as find / -perm -4000 -type f to find suids) and should be displayed here. But they are not listed here, instead the annoying "Command was: a perl script, too long to display" is popping up.
I think in general providing details on how the tests are run is a great idea! But I think this should probably be a feature that is only part of the expert mode and might be too confusing for the default output.
The text was updated successfully, but these errors were encountered: