Following check points have been added:
– checking old permission name for antivirus management in Plesk database
– If DotNetNuke is installed on at least one domain .Net Framework 3.5 presence will be checked
cPanel Inc. announced today the release of version 11.34 of cPanel & WHM software to the CURRENT tier with many improvements and upgrades that you, our Partners and end users, had a voice in.
As highlighted in his Keynote speech at last week’s 7th annual cPanel Conference, cPanel CEO, J. Nick Koston, outlined new features that include:
Upon updating or installing cPanel & WHM version 11.34 you will no longer be able to downgrade to a previous version.
For details regarding version 11.34 User Guide, Release Notes, Change Log and FAQ’s, please visit http://docs.cpanel.net.
Click here to pre-register for our upcoming webinar on version 11.34.
To update cPanel & WHM manually:
Log into WHM as the root user.
Click on the WHM 11.32.X (build X) link on the top right corner of the screen.
Click the button labeled Click to Upgrade.
At 3am CST, the Exim team released an update to correct CVE-2012-5671. An update to cPanel has been published to provide this update to our customers. Customers with Automatic Updates enabled, will receive the update with no interaction needed. We recommend all customers not using Automatic Updates, update as soon as possible.
To manually update your cPanel & WHM installation, run the following command in a command line:
<br />
/scripts/upcp --force<br />
For more information please see http://cpanel.net/exim-remote-co…-cve-2012-5671/
The tail command is a very commonly used command to pull the last number of lines from a file. This is extremely useful when you want to look through error logs to trouble shoot an issue. You can watch a file live or look back as many lines as needed.
tail [OPTION]... [FILE]...
View the last 10 lines of the error log:
tail error_log
Follow the error log live:
tail -f error_log
Show the last 300 lines of the error log:
tail -300 error_log
or
tail-n300 error_log
-f – Output the appended data when the file grows
-n – Output the last number of lines in the file
-c – Output the last K byte of the file
-v – Always output headers
If you are running an apache server password protecting directories is fairly simple. There are plenty of generators that will help you generate all of the code that you need to place into your .htaccess and .htpasswd files. This can be useful to hide content that you don’t want people to yet, or at all. This also allows you to only allow specific people access to certain areas of your web site.
First you need to start by editing your sites .htaccess file. The link below can help you generate the code, but for the most part it should look like this:
AuthUserFile /path/to/your/.htpasswd
AuthGroupFile /dev/null
AuthName Please enter a password to gain access
AuthType Basic
The AuthName is what will display in the password box that pops up when you try to access the protected directory. Now that you have that you will need to create the actual password file. This is usually named .htpasswd or can be changed to something a little less common as long as you reference it in the .htaccess file.
You can generate the encrypted password for the .htpasswd file by going to one of the generators and putting in the user and the password you would like to use. It will then give you a line that looks something like this:
admin:gj4DiJhygDhgdHt5hu74
Adding this to your .htpasswd file will grant the user admin permission to view that site. I haven’t seen a limit hit on how many users can be added. I imagine that if you add to many it may slow the authorization process down a bit. To add other users just make sure that each user and password are on a separate line.
A tip for choosing the password is that it won’t work with any special characters. This means no $%^&*!@# in your password. It will work with capitol letters and numbers so you can still make a fairly secure password.
58 queries. 8.25 mb Memory usage. 1.232 seconds.