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

[fix] Support per-file allowed lists for the badfuncs inspection #805

Merged
merged 1 commit into from Jun 23, 2022

Commits on Jun 23, 2022

  1. [fix] Support per-file allowed lists for the badfuncs inspection

    Some programs and libraries deliberately use functions that have been
    deemed forbidden by policy.  An example would be a library providing
    runtime support for older software.  In cases like this, you can
    specify an allowed block listing path globs and the specific forbidden
    functions they are allowed to use.  It is adviseable to add a comment
    idnicating why the forbidden function is allowed so future readers
    will understand why the rpminspect.yaml file is configured that way.
    
    The path specifications can be explicit paths (local path notation,
    relative to /) or patterns that are compatible with fnmatch(3) and
    glob(3).
    
    For example:
    
        ---
        badfuncs:
            allowed:
                /usr/sbin/somenetcmd:
                    - inet_aton
                    - gethostbyname
                /usr/lib*/libsomething.so.*:
                    - inet_network
    
    You can place this block in the package's rpminspect.yaml file to
    further control how the badfuncs inspection works for your build.
    
    Fixes: rpminspect#573
    
    Signed-off-by: David Cantrell <dcantrell@redhat.com>
    dcantrell committed Jun 23, 2022
    Copy the full SHA
    0ff3896 View commit details
    Browse the repository at this point in the history