Search results

Update, the atomic-php55 packages for EL5 (redhat/centos/cloudlinux) were finished earlier today. This was the harder package to create, so PHP 5.4 should take much less time. Im considering rolling this under a single installer that would put all versions on the system (5.2/5.3/5.4/5/5), with...

PHP 5.2 is doable, we just need to backport (a lot!) security fixes into it, and that will take time. Right now I have the atomic php 5.3, 5.4 and 5.5 packages living alongside one another on a Plesk system using fcgi of cgi. As I mentioned earlier, these are independent of the DSO build. They...

Check out Atomic Secured Linux, a security suite designed for Plesk environments (we are the founders of Plesk!). https://www.atomicorp.com/products/asl.html We also have a number of security application available in the Atomic repo, including the openvas vulnerability scanner. I highly...

We're tracking progress in the thread here: https://atomicorp.com/forum/viewtopic.php?f=2&t=7052 The first php54 packages are working (mostly) now, php55 will be ready soon

A follow up to this thread, we've put together PHP 5.3, 5.4, and 5.5 packages in our atomic-testing repo specifically to support the multiple PHP capabilities in Plesk 11.5. These are intended to live along-side of the existing vendor distributed PHP and not replace it. If anyone is interested...

While we as atomicorp the company do not support mysql as a product (yet anyway), we do have very active forums for the project as well as Mariadb. Also we use Plesk, and Centos 6 just like you do, so if you are running into a problem its going to be something we would probably run into as well.

There are certainly options that would let you limit the rate of logging in a LOG rule. For example in ASL we have blacklist rulesets with LOG rules at the bottom that fire at 10 in 1 minute, and a limit burst of 2. A limit for a TOR blacklist looks like this: -A ASL-TOR-DROP-LOG -m limit...

PHP 5.4 went up in the Atomic repo on August 1st. You can grab it from there now: https://www.atomicorp.com/wiki/index.php/PHP

A tactical update to this feature request, a short cut to implementation is to use the Chroot setting in mod_security as a straight DSO. You wouldnt need to make any kind of daemon level change in Apache itself. We've had this capability in Atomic Secured Linux for a few years now, and using...

Not really, I dont think qmail has any specific advantages over postfix. I use it because qmail was the only option when plesk first came out. Id say use whatever you are comfortable with.

Once again great question, netfilter is the underlying firewall system in Linux. The plesk firewall and its CLI counterpart, iptables are interfaces to netfilter. Netfilter itself can handle millions of entries. The front ends to netfilter on the other hand can be effected by all sorts of...

You can implement other AV scanners on plesk using either qmail-scanner (for qmail), or clapf (for postfix). Both packages are available in the atomic repo. Clapf supports drweb and clamav, qmail-scanner supports every AV scanner I believe. Personally I use qmail-scanner and clamav. They can be...

That is a very good question, the most efficient place to do this would be in the firewall. While you could block an IP in an .htaccess file, it would only apply to the web server. This would not have any impact on mail, and in general is a much more expensive operation in terms of CPU.

Try yum --enablerepo=atomic-testing upgrade httpd httpd-devel oh and make sure your yum config isnt excluding anything.

As a follow up suggestion there, referencing the CVE inside the %changelog of the rpm package is the standard for documenting backported fixes. Additionally doing that allows you to can directly reference a fix using the yum security plugin with the --cve, --security, --bz, and --advisory flags.

httpd 2.2.21 with the -devel package is available in the atomic-testing repo right now. You can install/upgrade with: wget -q -O - http://www.atomicorp.com/installers/atomic |sh yum --enablerepo=atomic-testing upgrade httpd and/or yum --enablerepo=atomic-testing install httpd-devel

A problem Ive been dealing with for 8 years now :P I'm trying to think of a quick way to explain it... so bare with me (it took me about 20 minutes to write this). 1. PHP can only be linked against a single mysql client library (5.0, 5.1, or 5.5) 2. If you link against a 5.5.x mysql client then...

We've got a couple threads about it in the forums: https://atomicorp.com/forum/viewtopic.php?f=2&t=5138 https://atomicorp.com/forum/viewtopic.php?f=2&t=4997 There was an even better one in there, but I cant seem to find it :P

Yeah thats just a bad vulnerablity scanner there for the 2nd issue. Its working off a pure banner grab to determine the version.

so from the remote system, try telneting to port 3306 (this is the mysql port). That would confirm that there is no network issue preventing you from accessing the host.