Archive for the tag 'Checking'


Checking For and Updating Packages

Checking For and Updating Packages

To see which installed packages on your system have updates available, use the following command:

yum check-update

Updating Packages

You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too.
Updating a Single Package

To update a single package, run the following command as root:

yum update package_name

Updating All Packages and Their Dependencies

To update all packages and their dependencies, simply enter yum update (without any arguments):

yum update

Implement Periodic Execution of Integrity Checking

By default, AIDE does not install itself for periodic execution.

Implement checking with whatever frequency is required by your security policy.
A once-daily check may be suitable for many environments. For example, to
implement a daily execution of AIDE at 4:05am, add the following line to /etc/crontab:

05 4 * * * root /usr/sbin/aide –check

AIDE output may be an indication of an attack against your system, or it may
be the result of something innocuous such as an administrator’s configuration
change or a software update.


Software Integrity Checking

Software Integrity Checking

The AIDE (Advanced Intrusion Detection Environment) software is included with the system to provide software integrity checking. It is designed to be a replacement for the well-known Tripwire integrity checker.

The RPM software also includes the ability to compare the hashes of installed files with those in its own metadata database. Integrity checking cannot prevent intrusions into your system, but can detect that they have occurred. Such integrity checking software should be configured before the system is deployed and able to provides services to users.

Ideally, the integrity checking database would be built before the system is connected to any network,though this may prove impractical due to registration and software updates.

How to ensure Package Signature Checking is Globally Activated

The gpgcheck option should be used to ensure that checking of an RPM package’s signature always occurs prior to its installation.

To force yum to check package signatures before installing them, ensure that the following line appears in /etc/yum.conf in the [main] section:


Tool for checking issues before upgrade or migration to Parallels Plesk 10.x version

Due to the changes in business model in Parallels Plesk Panel 10.x release, not all previous accounts settings will be portable from the previous Parallels Plesk Panel releases.

Attached is a script that allows checking environment before upgrade or migration. Now it is checking business logic issues and it works for both platform: Linux and Windows. This tool could be launched prior to upgrade for the purpose of getting a report on potential problems with the upgrade. Based on the report a hoster can decide whether upgrade to Parallels Plesk Panel 10.x is suitable.

How to use..

# php plesk10_preupgrade_checker.php [plesk-admin-password] -d safe_mode=Off

Next »