:set nocompatible

This should do the trick.

I wrote a perl script over the weekend to simulate logins into a website once every 2 mins. If login fails after 2 tries, an email alert will be sent to the administrator (Settings can be changed in Nagios). The script works by detecting a certain html pattern from the result generated by the login success webpage. An example of the command in action is something like this:

check_login -f 1 -u http://xxx.com/index.php -l xx -p xx -L Username -P Password -r ‘Logout.jsp’

* L is the Userid field in the form and P is the password field in the form.
* u is the FULL url including the http.
* l is the actual login name and p is the actual login password.
* r is the regex pattern to search for if the login is successful.
* f is the form number. If you have 2 forms in the login page, the 1 will be the first form.

For the script to work, you need perl and its mechanize library. Copy and paste this script into the default plugin folder - likely to be /usr/lib/nagios/plugins. Add ‘check_login’ to hosts.cfg and define it in commands.cfg (or checkcommands.cfg). Refer to the nagios doc if unsure. The script is backward compatible with netsaint.


#!/usr/bin/perl -Tw

use strict;
use Getopt::Long;
use WWW::Mechanize;
use vars qw($opt_v $opt_h $opt_u $opt_f $opt_r $opt_l $opt_L $opt_P $opt_p $PROGNAME);
use lib “/usr/lib/nagios/plugins” ;
use utils qw(%ERRORS &print_revision &support &usage);

my($PROGNAME) = $0 =~ m/([^\/]+)$/;

sub print_help ();
sub print_usage ();
delete $ENV{PATH};
delete $ENV{BASH_ENV};
delete $ENV{ENV};

Getopt::Long::Configure(’bundling’);

GetOptions(
‘v|version’ => \$opt_v,
‘h|help’ => \$opt_h,
‘u|url=s’ => \$opt_u,
‘l|login=s’ => \$opt_l,
‘p|password=s’ => \$opt_p,
‘f|formnumber=s’ => \$opt_f,
‘r|logoutregex=s’ => \$opt_r,
‘L|loginfield=s’ => \$opt_L,
‘P|passwordfield=s’ => \$opt_P,
);

if ($opt_v) {
print_revision($PROGNAME,’$Revision: 1.0 $’);
exit $ERRORS{’UNKNOWN’};
}
if ($opt_h) {
print_help(); exit $ERRORS{’UNKNOWN’};
}

#### PREDEFINE FIELDS
$opt_L = ($opt_L ? $opt_L : “Username”);
$opt_P = ($opt_P ? $opt_P : “Password”);

#### CHECKING REQUIRED FIELDS
sub error($$)
{
my($code, $msg) = @_;
print($msg, “\n”);
exit $ERRORS{$code};
}
($opt_f) || error(’UNKNOWN’, ‘You need to specify a form number.’);
($opt_u) || error(’UNKNOWN’, ‘You need to specify a url.’);
($opt_l) || error(’UNKNOWN’, ‘You need to specify a login name.’);
($opt_p) || error(’UNKNOWN’, ‘You need to specify a passwd.’);
($opt_r) || error(’UNKNOWN’, ‘You need to specify a logout regex.’);
my $agent = WWW::Mechanize->new();
$agent->get($opt_u);
$agent->form_number($opt_f);
$agent->field($opt_L,$opt_l);
$agent->field($opt_P,$opt_p);
$agent->click();

my $success = $agent->follow_link( url_regex => qr/$opt_r/i);
unless ($success) {
error(’CRITICAL’, “$opt_u login failed.\n”);
}

error(’OK’, “$opt_u login success.\n”);

sub print_usage ()
{
print <
Usage: $PROGNAME [-u URL] [-l login] [-p password] [-L loginfield] [-P=passwordfield] [-f formnumber] [-r logoutregex]

Required Arguments:
-u, –URL==STRING
URL of the site you want to login from.
-l, –login=STRING
login username.
-p, –password=STRING
login passwd.
-L, –loginfield=STRING
Name of the login field in the form.
-P, –passwordfield=STRING
Name of the passwd field in the form.
-f, –formnumber=INT
Form Number on the login page.
-r, –logoutregex=STRING
Regex URL to logout

END
}
sub print_help () {
print_revision($PROGNAME,’$Revision: 1.0 $’);
print <

Bernard Peh, November 2007

This nagios plugin simulates a remote login using perl mechanize library. It attempts to login from a url, check for a logout regex, then logout by itself.
This can be useful to make sure a website or database connection is alive.

END

print_usage();
support();
}

Under device, choose ipp and in Device URI, type ipp://hostname/ipp/. Then add the model and follow through the rest of the prompts. When you have finished, go to http://localhost:631/printers/ and you should see your printer listed there. do a test print. If it works, congrats. If not, click on modify printer and under Device URI try using socket://address:9100 instead of ipp. The later seems to work quite well with alot of printers. if in doubt, always telnet host 9000 to see if the port is accessible.

If you do not have access to cups via http://localhost:631, just edit the printers.conf file

vi /etc/cups/printers.conf

the config will be something like this:

Info HP laserjet 4100
Location myhouse
DeviceURI socket://your-ip:9100
State Idle
StateTime 1189572516
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy stop-printer

when done, do a “sudo /etc/init.d/cupsys restart”

hopefully, everything should be working.

Not every website uses encryption for password, so if you happen to register yourself in a hacker’s website, the hacker might use your username and password to try and login to other websites. Account Registration is always necessary but remember to keep a few low security user id and passwords for untrusted site. Some comon sense stuff but people don’t practice it.

:set noautoident

or add this in the vimrc file to make it a default.

President/ceo.

Dear sir,

RE-CONSTRUCTION OF IRAQ - VARIOUS SUPPLIES...

My name is ( ABD-AL-RAHMAN) and this is an urgent contract.We have recieved an allocation for a contract to supply your company’s Product,

this is a Multi Million Dollars worth of international supplies to Iraq.

My benefactor in this project is a high level Iraqi Government official who

has mandated me to seek for your confidential cooperation and participation in this contract.If your company

is capable of supplying or help to re-construct iraq, You would be paid cash before you supply. If you can

assist us, then kindly contact me immediately via the details below,and make sure to furnish me with your full company

profile,full names,direct telephone and fax numbers,and include your direct email address.

As soon as we recieve your response, we shall get back to you with all details to commence.

Thank you.

ABD-AL-RAHMAN

NB:100% upfront payment for all supplies.

Firstly, you will have to make sure that the package that you are trying to create is not yet available in the repository else you will be re-inventing the wheel. Next, decide a name for the package. The name must be unique and you can check it easily using

dpkg -S ${pkgName}

Rename the source directory containing the installation files as ${PackageName}-${PackageVersion}. Next, tar and compress the source directory and name it ${PackageName}-${PackageVersion}.tar.gz

Create a ‘deb’ dir under your home directory. Then, transfer the entire source directory and .gz file over.

If you are trying to create a pear module, you need to download and extract the source files from http://pear.php.net/packages.php. Do a fresh tar following the naming convention ${PackageName}-${PackageVersion}.tar.gz. For example, the original downloaded pear package is HTML_AJAX-0.5.2.tgz but I want my new package to be named pear-html-ajax-0.5.2, I would do this:

cd ~/deb
cp ../HTML_AJAX-0.5.2.tgz ./
tar -xzvf HTML_AJAX-0.5.2.tgz
rm HTML_AJAX-0.5.2.tgz
mv HTML_AJAX-0.5.2 pear-html-ajax-0.5.2
tar -czvf pear-html-ajax-0.5.2.tar.gz pear-html-ajax-0.5.2

If everything seems ok, your directory structure should be something like this:

- deb
- pear-html-ajax-0.5.2
+ AJAX
+ docs
+ examples
+ js
+ tests
AJAX.php
package.xml
pear-html-ajax-0.5.2.tar.gz

Install the dh-make package. Then, in the package dir (in this case, pear-html-ajax-0.5.2), run

dh_make -e yourname@infoxchange.net.au -f ../${pkgName.tar.gz}

* note the extra debian dir and orig.tar.gz file created
* consult man dh-make and man debhelper if necessary

- deb
- pear-html-ajax-0.5.2
+ AJAX
+ debian
+ docs
+ examples
+ js
+ tests
AJAX.php
package.xml
pear-html-ajax_0.5.2.orig.tar.gz
pear-html-ajax-0.5.2.tar.gz

The debian dir contains important information about the installation process. cd debian and you will see many files. The .ex files are sample templates and can usually be ignored.

* changelog - As the name implies.
* copyright - As the name implies.
* compat - Set the rules under which debhelper scripts (dh_*) operates. (no modification needed)
* control - Contains important installation parameters. Change the following fields: section, depends and description.
* dirs - directory where the files will be installed.
* rules - Rules for the installation procedure. This is the hardcore part. Major changes needed.

If you are creating a pear package, you need to move package.xml into the package dir (in this case, pear-html-ajax-0.5.2). I have created a sample pear rule and you can copy and paste it into your rule file just to save time (see below).

So when you’re ready to try creating a package, do:

cd ~/deb/$your_new_directory
dpkg-buildpackage -rfakeroot (or sudo dpkg-buildpackage)

The dpkg-buildpackage command will try to create a .deb package in the directory above your current directory, using the files in the ‘debian’ directory inside your current directory.

A proper install will include some other files other than the .deb file.

- deb
+ pear-html-ajax-0.5.2
pear-html-ajax_0.5.2.orig.tar.gz
pear-html-ajax_0.5.2-1.diff.gz
pear-html-ajax_0.5.2-1.dsc
pear-html-ajax_0.5.2-1_i386.changes
pear-html-ajax_0.5.2-1_i386.deb
pear-html-ajax-0.5.2.tar.gz

* see http://www.debian.org/doc/maint-guide/ch-build.en.html

If that seems to complete properly, you should be able to try installing it on your own machine with:

cd ~/deb
dpkg -i ${your_new_package}.deb

Check that all the files have been installed in the right place. Eg, all pear files should go to /usr/share/php.

Also note that there are other ways of creating debian packages… this is the standard way.

——- SAMPLE RULES FILE FOR PEAR —–

#!/usr/bin/make -f