Search results

For future reference since none of that made sense :P rpm -q --scripts <package name>

Many updates today, hopefully resolving some long standing php.ini issues on 64 bit platforms. Security fix backporting is now complete for 5.2! Changelog: * PHP 5.6 has been updated to beta 3 * PHP 5.2 backport of CVE fixes is now complete * php.ini fixes have been applied to PHP 5.2, 5.5...

Very, this has been around for many years now. Lots of vetting during that time.

Check out the sysdig package from the atomic repo, it will let you dig very deep into what the system is doing. To install: wget -q -O - http://www.atomicorp.com/installers/atomic |sh yum install sysdig Then to look at where httpd is spending most of the system I/O: sysdig -c topfiles_time...

Delta RPM updates are now available for the PHP Panda on Centos/Redhat/Cloudlinux 6. deltas (drpms) are binary "patches" to the existing RPM packages. Instead of downloading all files, regardless of whether they have changed or not, a delta RPM will only download the files that have...

Latest release updates: PHP 5.6 beta 2 PHP 5.5.12 PHP 5.4.28 Enjoy!

Yes, this is distributed as an SCL package (Software Collections Library), which means it is independent fromt updates to plesk or from the distro (centos/redhat/etc).

Atomic PHP 5.2.17-5 is now available. This update is part of the ongoing process to backport bugs and security fixes into the PHP 5.2 branch. This update addresses the following CVES: - Fix CVE-2006-7243 - Fix CVE-2011-2202 - Fix CVE-2011-4153

You can also use the exclude= directive in the channel settings

No issues that Im aware of, whats the problem?

PHP 5.6 beta 1 was released today, to upgrade: yum upgrade atomic-php56-php

You can also enable logging of the mail() function in php.ini by adding: mail.log /var/log/httpd/mail.log or you can embed a header in every message using: mail.add_x_header 1 I have a deeper blog post on using these and other methods here...

Indeed it can be, when you're writing firewall rules the thing to keep in mind is that Order Matters :P So what exactly are you trying to do?

Its optional, you don't have to remove it unless you want to (like if you dont have a license for it). qmail-scanner isnt compatible with drweb (I dont think... its been a while). But clapf for postfix is, it would use both clamav and drweb if they are installed on the system.

Good news here, this is not necessary on a CentOS 6 system. The update openssl-1.0.1e-16.el6_5.7 resolves the issue, however you would be advised to regenerate the certificates on the system: * Mon Apr 07 2014 Tomáš Mráz <[email protected]> 1.0.1e-16.7 - fix CVE-2014-0160 - information...

So the this depends on your OS first. EL5 (RHEL/CentOS/Cloudlinux) is not affected by this vulnerability unless you had upgraded to the plesk distributed httpd & openssl to support SNI. If you had done this, then yes you will need to get an updated openssl for that system from parallels, and...

Actually a 3rd way here, we have a repo that just has PHP 5.3 backports, as well as PHP Panda called Nucleus. In that context you'd only have exposure to those packages

Yeah there are a couple methods we use to do this in Atomic Secured Linux installs. Basically the same idea, where you want to be selective about packages on a regular upgrade event (like kernels or something). The first method, is to disable an entire channel by default (enabled=0) and opt in...

You could add an exclude=php* to /etc/yum.repos.d/atomic.repo and that would block all the php* packages, but not block the atomic-php* updates from the system.

That'd be unrelated to PHP Panda, since its upgrading PHP (the dso version) from atomic so I dont want to confuse issues. P3 installs to /opt/atomic, and it does not overlap with psa-php53-configurator. That said, its something I think we can resolve in a PHP update later.