Safe Repository Check

Navigation:  Fixing Vulnerabilities >

Safe Repository Check

Previous pageReturn to chapter overviewNext page

By default Imunify QuickPatch+ selects package update targets in a conservative fashion. The update target package must come from the repository of the currently installed package or a configured repository that the extension considers safe:

 

Ubuntu: safe repositories include the base, updates or security repositories for the distro. For example, if the distro alias is Trusty, valid repositories include: trusty, trusty-updates, trusty-security.

Debian: safe repositories include the standard repositories for the distro (e.g., Jessie) or distro suite (e.g., stable).

CentOS: safe repositories include the base, updates and extras repositories

RedHat: only the repository of the currently installed package is considered safe, as other distro specific repository names or IDs vary widely.

This safe repository check can be disabled through the extension settings plx_icon_cog. When the safe repository check is disabled, the extension selects the package with the highest version/release from among all configured repositories as its update target.

 

Disabling the safe repository check can be particularly useful on RedHat systems where, otherwise, update targets are only chosen from the repository of the currently installed package.