Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Command was: a perl script, too long to display" #2

Open
maba4891 opened this issue Nov 7, 2015 · 0 comments
Open

"Command was: a perl script, too long to display" #2

maba4891 opened this issue Nov 7, 2015 · 0 comments

Comments

@maba4891
Copy link
Collaborator

maba4891 commented Nov 7, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant