Linux Basement Presents: Chad’s Blog

I found this article, which gives a great run through on installing Nessus on Ubuntu.

http://www.darknet.org.uk/2006/11/installing-nessus-on-debian-based-oss-like-ubuntu/

Installing:

I personally use apt-, however, you may choose any other package manager.

This will install the nessus client and server, and the -y is used to answer YES to the confirmation of apt-get.

We have now installed both the client and the server. Let’s proceed to the addition of a user:

Display:

Login : Whateva
Authentication (pass/cert) [pass] :

About this display:

When asked about Authentication (pass/cert) [pass] : just press enter, as we will not use any.
When asked about rules for the specific user, press CTRL+D, as we will not enter any rules for

Starting the Daemon:

By default, nessusd has not started. To manully force him to, you will need to do the following:

Registering Nessus:

Nessus will work without being registered, however, it will have
limitations. Unnecessary limitations, since it is easily registered.

Nessus Registration page - Go here and start the proccess.

After you have entered your e-mail address, the instructions on how to register will not work on Debian-based OSs.

On the eMail from the Nessus team, you will be instructed to this path:

, however, the path should be replaced by

, making the complete registration command:

You should now have a complete and working installation of Nessus. Enjoy and remember, automatic scanners are not 1337! =)

TIP: Before starting to use Nessus, update the plugins by doing the following:

Forget everything below, and follow these directions

http://www.howtoforge.com/eaccelerator_php5_debian_etch

*******************************************************************

Download the latest version of eaccelerator over at http://www.eaccelerator.net/wiki/

I used the following directions to increase web server performance by installing eaccelerator

phpize
./configure   --enable-eaccelerator=shared
make
make install

When you do the make install, you will get a path back to your sources, make sure you have that path.

You will enter it below for the zend_extension

The configuration parameters are as follows:

zend_extension                  = "/usr/lib/php5/SOMENUMBER/eaccelerator.so"
eaccelerator.shm_size           = 0
eaccelerator.cache_dir          = "/var/cache/eaccelerator"
eaccelerator.enable             = 1
eaccelerator.optimizer          = 1
eaccelerator.check_mtime        = 1
eaccelerator.shm_max            = 0
eaccelerator.shm_ttl            = 0
eaccelerator.shm_prune_period   = 0
eaccelerator.shm_only           = 0
eaccelerator.compress           = 1
eaccelerator.compress_level     = 7

 Make sure you manually create the /var/cache/eaccelerator directory, and chmod it 644.

More info here.

http://www.eaccelerator.net/wiki/InstallFromSource

Step 1. Compiling eAccelerator ¶

You need to run these commands in the eAccelerator source directory.
eAccelerator supports multiple php branches so you need to bootstrap
eAccelerator first. This can be done with the phpize script. It very
important that you use the phpize script of the php version for which
you want to compile eAccelerator.
The phpize and php-config scripts are available in the development
packages of your distro. For fedora this is php-devel, for debian
php-dev, other distribution should be similar.

When you have only one php install, it’s safe to run these commands in the source directory:

phpize
./configure
make

The phpize and php-config are the ones that are in
your path. When you have more then one php install or the phpize and
php-config scripts aren’t in your path then you should follow this
procedure. This example has php installed in /opt/php, this is the path
of the –prefix option given to the php configuration script.

export PHP_PREFIX=”/opt/php”
$PHP_PREFIX/bin/phpize
./configure –enable-eaccelerator=shared –with-php-config=$PHP_PREFIX/bin/php-config
make

For more information about the options for the configure script you should read the CompileConfiguration page.

After compilation, there should be a “eaccelerator.so” file in the modules subdirectory of the eAccelerator source directory.

Step 2. Installing eAccelerator ¶

make install

This will copy the previously created eAccelerator binary to the php
extension directory. When this command ends, it will print out the
directory in which eAccelerator has been installed.

Step 3. Configuring eAccelerator ¶

eAccelerator can be installed both as Zend or PHP extension. When
you install eAccelerator as a zend_extension you need to give the full
path to the eaccelerator.so library.

If you have /etc/php.d directory, you should copy eaccelerator.ini
to it and modify the default values. If not, you need to edit your
php.ini file (usually /etc/php.ini).

To install as Zend extension:

zend_extension=”/usr/lib/php4/eaccelerator.so”
eaccelerator.shm_size=”16″
eaccelerator.cache_dir=”/tmp/eaccelerator”
eaccelerator.enable=”1″
eaccelerator.optimizer=”1″
eaccelerator.check_mtime=”1″
eaccelerator.debug=”0″
eaccelerator.filter=”"
eaccelerator.shm_max=”0″
eaccelerator.shm_ttl=”0″
eaccelerator.shm_prune_period=”0″
eaccelerator.shm_only=”0″
eaccelerator.compress=”1″
eaccelerator.compress_level=”9″

If you use a thread safe build of PHP you must use “zend_extension_ts” instead of “zend_extension”.

To install as PHP extension:

extension=”eaccelerator.so”
eaccelerator.shm_size=”16″
eaccelerator.cache_dir=”/tmp/eaccelerator”
eaccelerator.enable=”1″
eaccelerator.optimizer=”1″
eaccelerator.check_mtime=”1″
eaccelerator.debug=”0″
eaccelerator.filter=”"
eaccelerator.shm_max=”0″
eaccelerator.shm_ttl=”0″
eaccelerator.shm_prune_period=”0″
eaccelerator.shm_only=”0″
eaccelerator.compress=”1″
eaccelerator.compress_level=”9″

Step 4. Creating cache directory ¶

One last very important step is creating the cache directory that
you configured in the previous step. The default value is
/tmp/eaccelerator It’s easy because it’s writable to everyone, but it
isn’t very smart because on a lot of systems this directory is cleaned
on reboot. A better place would be /var/cache/eaccelerator. Create the
directory and make sure it’s writable for the user eAccelerator runs
under (usually the user which you webserver runs as).

A safe bet is making it world writable. A safer and cleaner way
would be to change the owner of the directory to the same user PHP runs
as (most of the time the same user as Apache or Lighttpd) and set 0644
permissions.

The lazy way:

mkdir /tmp/eaccelerator
chmod 0777 /tmp/eaccelerator

After hearing about git on Leo Laporte’s FLOSS weekly, I am very interested in learning more about it, and how I can incorporate it with open source web design. I would like to see the ability to make a change to my drupal installation, see how it effects the installation, before I publish it to my actual site. I am doing some investigation, and will post more when I decide to move forward.

I found this great post over on bodybuilding.com’s boards. It is a grocery list for someone who is trying to loose weight and build muscle. Posting it here so I don’t loose it!

Lean Protein:
Chicken
Eggs/Egg Whites
Tuna
Turkey
Salmon
Tilapia
Lean Beef
Lean Meat
Turkey Burgers
Turkey Sausage

Complex Carbs:
Oatmeal - Quaker Oats or Steel Cut
Whole Grain Cerael - Bran Flakes, Fiber One, Kashi Go Lean
Whole Grain Bread - or other varieties ex. Ezekiel bread (frozen organic is healthiest)
Sweet Potaotes
Yams
Brown Rice / White rice(if u have to)

Fibrous Carbs:
Iceberg Lettauce
Roamine Lettauce
Spinach
Broccoli
Califlour
Green Beans
Asaparagus

Other Veggies(in moderation)
Carrots
Corn
Peas

Fruits:
Apples
Bananas
Oranges
Blueberries
Strawberries
Pineapple
Mango

Dairy:
Milk (skim - Whole) Preference Based
Cottage Cheese
Cheese (moderation)

Fat Sources:
Natural Peanut Butter
Olive Oil
Fish Oil
Flax Oil
Fish Caps
Sunflower Oil
Peanuts
Almonds
Walnuts
Cashews

I recently rolled out a huge new website for the school district I work for. Actually, 15 new sites, all using drupal, an open source content management system that I often talk about on this blog. I got in the paper, and thought I’d post it here to archive it. I love the last quote!!!