RPM::Grill::Plugin::SecurityPolicy(3pm)

1RPM::Grill::Plugin::SecUusreirtyCPoonltirciyb(u3tpemd)PRePrMl::DGorciulmle:n:tPaltuigoinn::SecurityPolicy(3pm)
2
3
4

NAME

6       FIXME - FIXME
7

SYNOPSIS

9           use Fixme::FIXME;
10
11           ....
12

DESCRIPTION

14       FIXME fixme fixme fixme
15

CONSTRUCTOR

17       FIXME-only if OO
18
19       new( FIXME-args )
20           FIXME FIXME describe constructor
21

METHODS

23       FIXME document methods
24
25       method1
26           ...
27
28       method2
29           ...
30

EXPORTED FUNCTIONS

EXPORTED CONSTANTS

EXPORTABLE FUNCTIONS

FILES

DIAGNOSTICS

36       PolkitError
37           Unexpected error. We run xsltproc against a polkit file; the
38           command is always expected to return with exit code 0 (success).
39           This error indicates that we got nonzero (error) status.
40
41       PolkitSelf
42           The policy shipped in your package contains a default result
43           <tt>auth_self</tt> or <tt>auth_self_keep</tt>.  These will allow
44           <b>any</b> user to perform the action by supplying their own
45           password, which they presumably know because they were able to log
46           in and invoke the action in the first place.  The
47           <tt>auth_self*</tt> results are therefore inappropriate for any
48           actions that could affect the system-wide behavior or other users.
49
50           Usually, a more appropriate default result is
51           <tt><b>auth_admin</b></tt> or <tt><b>auth_admin_keep</b></tt>;
52           these protect the system against unprivileged users.  (Single-user
53           desktops can still be configured to only use the user's password by
54           adding the user to the "wheel" group.)
55
56       RubyAdvisoryDB
57           Package may be affected by a Ruby Gem CVE. This test compares the
58           Gem name and version (but not the release) against a master list of
59           known vulnerabilities <https://github.com/rubysec/ruby-advisory-
60           db>.  If the name+version match a known CVE, this warning is
61           triggered.
62
63           If you have backported a fix, please include the string "Fix
64           CVE-YYYY-NNNN" in your specfile's %changelog section. This will
65           silence the warning for a given CVE.
66

AUTHOR

71       Ed Santiago <santiago@redhat.com>
72

POD ERRORS

74       Hey! The above document had some coding errors, which are explained
75       below:
76
77       Around line 462:
78           An empty L<>
79
80
81
82perl v5.38.0                      2023-0R7P-M2:1:Grill::Plugin::SecurityPolicy(3pm)