Search results

I have this in options.conf secure_htaccess=yes When running ./build rewrite_confs the wrong symlink was created in /etc/httpd/conf/extra/ CB linked httpd-phpmodules-old.conf instead of httpd-phpmodules-new.conf

Much better :) There is still one bug Since the installed version is higher than what is offered, CB should just ignore it unless there are known issues with using a higher build on the platform on which the script is run.

I've just tried using CB 2.0.0-RC7 (rev: 910) and it did not work at all webapps.list webmail=/var/www/html/webmail myadmin=/var/www/html/myadmin Microsoft-Server-ActiveSync=/var/www/html/webmail/rpc.php autodiscover/autodiscover.xml=/var/www/html/webmail/rpc.php...

I've just upgraded a server to Apache 2.4.10 and after a rewrite_confs all PHP settings were wiped out from the httpd.conf files. We're using custom virtualhost templates which only include |*if HAVE_PHP1_FPM="1"| but apparently that doesn't work, DA is still looking for |*if...

Blocking domains does not work against spambots networks, but it does work against known companies with a bad reputation. These companies often use subdomains to send their messages, so it's useful to be able to use something like: *.badcompany.tld SB uses lsearch to retrieve domains from text...

What about SHA2 for the CSR? openssl req -sha256 -nodes -newkey rsa:4096 -nodes -keyout domain.key -out domain.csr -subj "<collected data>"

Things have changed, some people feel safer with a 4096 key size SHA2 should also be added as an option for the CSR.

5 seems the standard in a lot of places (1 per continent), so DA should go with that if possible.

Very useful, thank you :)

DA should validate the concept first. There might be some hurdles they're aware of and missing API endpoints that we would need to build the interface.

DA needs a new skeleton theme which works purely by making ajax calls to its API. Once this happens, we'll have lots of pretty themes which work on all kind of devices. Until then, theme modders are just painting lipstick on a pig.

That's the almost which is a problem ;). Almost runs most major frameworks and CMS as long as you only use the top extensions Almost has the most commonly used PECL extensions etc. No hosting company can offer only that instead of PHP to the general public, so it's something which consumes more...

Since DA now offers a way for the customer to select a PHP version to use, I guess the customer can switch to HHVM to see if things still work and that won't create a support headache as it's easy to print a large disclaimer saying that they're on their own if using this particular setup. Having...

A couple of suggestions Naming: It might be worth using something generic for files. We use domainips and reverse_domainips, but anything which describes the content rather than the use might be more useful in the long run IPV6: Make the scripts IPv6 compatible or you'll end up with broken IP...

Could be interesting as an alternative for people who don't offer traditional hosting or only have geeks as customers. It's currently compatible with so few frameworks and extensions that lots of things will break and that will lead to an increase in support requests. http://hhvm.com/frameworks

More than 162,000 WordPress sites used in DDoS attack http://www.computerweekly.com/news/2240215998/More-the-162000-WordPress-sites-used-in-DDoS-attack

Seems to be the same. mod_security also has a ban system based on RBLs, but it crashes under load :S

AFAIK, modules have to be compiled afterwards. You'de be better off wrapping CB into your own script Optimized CFLAGS ./build apache mod_something_sub{ } exit; You could even call scripts to recompile all PHP and all Apache modules extensions instead of defining everything in that file.

There seems to be a lot of mini-DDOS attacks created by brute-force Wordpress scanners at the moment. You may want to implement fail2ban.

Steps for BFM: Login as admin Go to BFM Select IP to ban Click on "Block IPs" button At the bottom of the "results" page, click on "admin » Back" Steps for SSL: Login as user Go to SSL page Click on link to install CA root Paste and install a CA cert At the bottom of the "results" page...