apparmor/utils/aa-decode.pod

=pod

=head1 NAME

aa-decode - decode hex-encoded in AppArmor log files

=head1 SYNOPSIS

B<aa-decode> [option] E<lt>HEX STRINGE<gt>

=head1 DESCRIPTION

B<aa-decode> will decode hex-encoded strings as seen in AppArmor log
output. It will also take an audit log on standard input and convert
any hex-encoded AppArmor log entries and display them on standard
output.

=head1 OPTIONS

=over 4

=item --help

displays a short usage statement.

=back

=head1 EXAMPLES

  $ aa-decode 2F746D702F666F6F20626172
  Decoded: /tmp/foo bar

  $ cat /var/log/kern.log | aa-decode
  ... denied_mask="r::" fsuid=1000 ouid=1000 name=/tmp/foo bar

=head1 BUGS

None. Please report any you find to gitlab at
L<https://gitlab.com/apparmor/apparmor/-/issues>.

=head1 SEE ALSO

apparmor(7)

=cut
add aa-decode and manpage For now just look at 'name=...' which is usually the last in the log entry, so validate input against this and output based on it. TODO: better handle other cases too 2010-01-12 07:19:20 -06:00			`=pod`

			`=head1 NAME`

			`aa-decode - decode hex-encoded in AppArmor log files`

			`=head1 SYNOPSIS`

manpages: incorporate podchecker; fix errors and (most) warnings This patch adds a 'check_pod_files' make target to the common make rules, and then fixes the errors it highlighted as well as most of the warnings. It will cause 'make check' in most of the directories to fail if there are errors in a pod file (but not if there are warnings). Common issues were: - using an '=over/=back' pair for code-like snippets that did not contain any =items therein; the =over keyword is intended for indenting lists of =item entries, and generates a warning if there isn't any. - not escaping '<' or '>' - blank lines that contained spaces or tabs The second -warnings flag passed to podchecker is to add additional warnings, un-escaped '<' and '>' being of them. I did not fix all of the warnings in apparmor.d.pod, as I have not come up with a good warning-free way to express the BNF of the language similar in format to what is currently generated. The existing libapparmor warnings (complaints about duplicate =item definition names) are actually a result of passing the second -warnings flag. The integration into libapparmor is suboptimal due to automake's expectation that there will be a test driver program(s) for make check targets; that's why I added the podchecker call to the manpage generation point. Signed-off-by: Steve Beattie <steve@nxnw.org> Acked-by: Seth Arnold <seth.arnold@canonical.com> --- changehat/mod_apparmor/Makefile \| 3 changehat/mod_apparmor/mod_apparmor.pod \| 28 ++- common/Make.rules \| 4 libraries/libapparmor/doc/Makefile.am \| 7 parser/Makefile \| 2 parser/apparmor.d.pod \| 275 +++++++++++++------------------- utils/Makefile \| 3 utils/aa-cleanprof.pod \| 2 utils/aa-complain.pod \| 2 utils/aa-decode.pod \| 2 utils/aa-easyprof.pod \| 69 +++----- utils/aa-enforce.pod \| 2 utils/aa-genprof.pod \| 2 utils/aa-logprof.pod \| 6 utils/aa-sandbox.pod \| 64 ++----- utils/logprof.conf.pod \| 2 utils/vim/Makefile \| 2 17 files changed, 212 insertions(+), 263 deletions(-) 2014-09-15 11:30:47 -07:00			`B<aa-decode> [option] E<lt>HEX STRINGE<gt>`
add aa-decode and manpage For now just look at 'name=...' which is usually the last in the log entry, so validate input against this and output based on it. TODO: better handle other cases too 2010-01-12 07:19:20 -06:00
			`=head1 DESCRIPTION`

			`B<aa-decode> will decode hex-encoded strings as seen in AppArmor log`
			`output. It will also take an audit log on standard input and convert`
			`any hex-encoded AppArmor log entries and display them on standard`
			`output.`

			`=head1 OPTIONS`

			`=over 4`

			`=item --help`

			`displays a short usage statement.`

			`=back`

			`=head1 EXAMPLES`

			`$ aa-decode 2F746D702F666F6F20626172`
			`Decoded: /tmp/foo bar`

			`$ cat /var/log/kern.log \| aa-decode`
			`... denied_mask="r::" fsuid=1000 ouid=1000 name=/tmp/foo bar`

			`=head1 BUGS`

docs: update documentation to point bug reporting to gitlab Move suggested bug reporting from launchpad to gitlab Signed-off-by: John Johansen <john.johansen@canonical.com> Acked-by: Steve Beattie <steve.beattie@canonical.com> 2020-05-02 20:40:55 -07:00			`None. Please report any you find to gitlab at`
			`L<https://gitlab.com/apparmor/apparmor/-/issues>.`
add aa-decode and manpage For now just look at 'name=...' which is usually the last in the log entry, so validate input against this and output based on it. TODO: better handle other cases too 2010-01-12 07:19:20 -06:00
			`=head1 SEE ALSO`

			`apparmor(7)`

			`=cut`