Files that are changed by rpms that should be marked as configuration files in Red Hat Satellite 6.

Solution Verified - Updated -

Issue

  • Files that are changed by RPM's should be marked as configuration files since the integrity checking process skips checking of configuration files and checks only the non-configuration files to report a security breach if any changes are made on them.
  • Below are some examples of files which are changed by RPM's and hence should be marked as configuration files so that the integrity checks do not report a security breach.

    S.5....T.    /var/lib/foreman/public/apipie-cache/apidoc/v2/hostgroups.ca.html
    S.5....T.    /var/lib/foreman/public/apipie-cache/apidoc/v2/hostgroups.ca.json
    S.5....T.    /var/lib/foreman/public/apipie-cache/apidoc/v2/hostgroups.de.html
    S.5....T.    /var/lib/foreman/public/apipie-cache/apidoc/v2/hostgroups.de.json
    S.5....T.    /var/lib/foreman/public/apipie-cache/apidoc/v2/smart_proxies/update.zh_TW.html
    S.5....T.    /var/lib/foreman/public/apipie-cache/apidoc/v2/smart_proxies/update.zh_TW.json
    S.5....T.    /etc/smart_proxy_dynflow_core/settings.yml
    .
    .
    and many more
    

Environment

  • Red Hat Satellite 6.3.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content