From: Simon Ruderich Date: Thu, 17 May 2012 11:10:37 +0000 (+0200) Subject: Clarify that no output means no flags are missing. X-Git-Tag: 0.03~7 X-Git-Url: https://ruderich.org/simon/gitweb/?a=commitdiff_plain;h=11b760e9716cac5513dd0cf9267b8f4780b43b35;p=blhc%2Fblhc.git Clarify that no output means no flags are missing. --- diff --git a/README b/README index 9ef1fe8..6c84894 100644 --- a/README +++ b/README @@ -41,6 +41,8 @@ blhc can be run directly from the source tree (`bin/blhc`) or copied anywhere on the system. It doesn't have to be explicitly installed. To read the man page use `perldoc bin/blhc`. +If there's no output, no flags are missing and the build log is fine. + For more examples see the man page. diff --git a/bin/blhc b/bin/blhc index 0d66b78..2168110 100755 --- a/bin/blhc +++ b/bin/blhc @@ -1074,6 +1074,8 @@ It's designed to check build logs generated by Debian's dpkg-buildpackage (or tools using dpkg-buildpackage like pbuilder or the official buildd build logs) to help maintainers detect missing hardening flags in their packages. +If there's no output, no flags are missing and the build log is fine. + =head1 OPTIONS =over 8 @@ -1175,6 +1177,8 @@ Normal usage, parse a single log file. blhc path/to/log/file +If there's no output, no flags are missing and the build log is fine. + Parse multiple log files. The exit code is ORed over all files. blhc path/to/directory/with/log/files/*