Blog backup :)

Make a copy of your entry blog on your hard disc, with this magnificent tool , is a Open Source program, the name is HTTrack, http://www.httrack.com/ enjoy it

Blog backup :)

Make a copy of your entry blog on your hard disc, with this magnificent tool , is a Open Source program, the name is HTTrack, http://www.httrack.com/ enjoy it

Feed Burner :)

Para la gente que tiene un blog gratuito, y que tal vez no tiene acceso para hacer un backup de su base de datos, aqui esta la solucion , es un quemador de feeds llamado feedburner, y tener sus feeds quemados ahi como una especie de backup, para registrarse solo tienen que ir a http://www.feedburner.com se registran queman su feed o los feeds que quieran y listo , saludos.

Feed Burner :)

Para la gente que tiene un blog gratuito, y que tal vez no tiene acceso para hacer un backup de su base de datos, aqui esta la solucion , es un quemador de feeds llamado feedburner, y tener sus feeds quemados ahi como una especie de backup, para registrarse solo tienen que ir a http://www.feedburner.com se registran queman su feed o los feeds que quieran y listo , saludos.

Fisica Cuantica

Conoces algo sobre la fisica cuantica?, enterate un poco de que o como es, aqui http://www.ytuquesabes.es/

So, what´s your price? – ¿Y tu cuanto cuestas?

A very nice movie, el hunk tenia razon

Comment posted by
at 7/29/2007 9:33:16 PM

saludos dmesg, si buena la pelicula, tiene muchos mensajes.

Comment posted by
at 7/29/2007 9:34:38 PM

saludos dmesg, si es muy buena la pelicula, tiene muchos mensajes

Block ssh bruteforce attempts

Most people with a box on public IP, and with a sshd listening on port 22, notices a lot of bruteforce attempts. These attempts are filling up logs, and are a pure annoyance. Here’s how I “solved” it..

In OpenBSD 3.7, pf got a really nice feature called max-src-conn-rate, which specifies how quickly new connections can be made. Connecting hosts exceeding this limit can be put into a table, and all states including that hosts IP address, can also be flushed.

When I have the offending IPs in a table, it can easily be blocked early on in our ruleset. But since I don’t want to block a host forever, or even until the next reboot, I’m gonna use a small utility to clean out this table once in a while.

Let’s start with the magic pf rule:

# special rule for ssh
pass in on $ext_if proto tcp from any to ($ext_if) port ssh \
flags S/SA keep state \
(max-src-conn-rate 3/30, overload flush global)

The keyword here is ofcourse “max-src-conn-rate”. The arguments tell pf to put every IP exceeding a connection rate of more than 3 connections in every 30 seconds, in a table called “ssh-bruteforce”. How often do valid users connect to ssh that often? Ofcourse you can set this to 6/60 or something more apropriate for your environment. Last but not least pf kills all states originating from the bad host.

To keep the bad boys out, I add a block rule early on in my ruleset:

# block the ssh bruteforce bastards
block drop in quick on $ext_if from

Great, now the table are getting populated with bad hosts, and they’re getting blocked. But as I said earlier, I don’t want to block them forever. This is were expiretable comes in handy. This utility, written by Henrik Gustafsson, takes a look at a table, and removes (”expires”) entires older then the specified amount of time.

It’s in ports (sysutils/expiretable), but was commited after 3.8 was tagged, so you’ll have to go -current, or compile/install it by hand. Then add this to roots crontab:

*/5 * * * * /usr/local/sbin/expiretable -t 3600 ssh-bruteforce

Every five minutes, I expire entries older than one hour.

This is how I get rid of thousands of login attempts filling my logs.

Comment posted by
at 7/6/2007 3:00:01 PM

Está muy bien, lo implementaré para Mexinética porque sí, tenemos una cantidad obscena de gente llenando los logs a lo estúpido..

Comment posted by
at 7/6/2007 2:59:00 PM

Está muy bien, lo implementaré para Mexinética porque sí, tenemos una cantidad obscena de gente llenando los logs a lo estúpido..

Create a NetBSD LiveCD

Introduction
You may have various reasons to create a LiveCD.
Create a custom installer for your application and distribute it to the customers, create a desktop enviroment and boot it off your CD whenever you cannot access your own computer or maybe you have a diskless router and you want to run your O.S off the CD.
Implementation
There are two ways to create a LiveCD running NetBSD.
The “old” way is to create a boot floppy sized image.
The boot image must be exactly the size of either a 1200, 1440, or a 2880 kB floppy, and mkisofs will use this size when creating the output iso9660 filesystem.
The image will have a kernel with root file system inserted into it.
For i386, compile your custom kernel or you can use kernel config from /usr/src/sys/arch/i386/conf/INSTALL.
Then do following:

Create a directory where you will build your image and cd to it.
# cd /my_build/dir
Copy your custom kernel to this directory.
# cp /usr/src/sys/arch/i386/compile/obj/${MYKERNEL}/netbsd .
Create file system of the directory with files for your LiveCD.
# makefs -s ${FS_SIZE} -t ffs md.img ${IMG_DIR}
where ${FS_SIZE} is the size of your md.img and IMG_DIR is where you have your file system.

Now you need to insert the image into your kernel, wich then will get extracted of the kernel and mounted as memory file system:
# mdsetimage -v -s netbsd md.img
Compress your kernel to save space and rename it (optional step):
# gzip -f -9 netbsd ; mv netbsd.gz netbsd
For vnconfig, newfs and disklabel to “understand” the notion of floppy288 you need to edit your /etc/disktab and add there:

floppy288|2.88MB 3.5in Extra High Density Floppy:\
:ty=floppy:se#512:nt#2:rm#300:ns#36:nc#80:\
:pa#5760:oa#0:ba#4096:fa#512:ta=4.2BSD:\
:pb#5760:ob#0:\
:pc#5760:oc#0:

Create virtual disk and file system on it.
# dd if=/dev/zero of=image.fs count=5760
# vnconfig -t floppy288 -v -c /dev/vnd0d image.fs
# disklabel -rw /dev/vnd0d floppy288
# newfs -m 0 -o space -i 204800 /dev/rvnd0a
Bootstrap your virtual disk:
# /usr/sbin/installboot -v -m i386 -o timeout=3,console=pc -t ffs /dev/rvnd0a /usr/mdec/bootxx_ffsv1
Mount the virtual disk you just created and copy over your kernel and second stage boot loader.
# mount /dev/vnd0a /mnt
# cp /boot /mnt/
# cp netbsd /mnt/
# umount /mnt
# vnconfig -u vnd0d
Create a directory for your ISO image and copy your image there.
# cp image.fs cdisodir/
You can put some additional files to the cdisodir, they will be avaliable when you mounted your CD.

Create ISO image.
# mkisofs -l -J -R -o livecd.iso -c boot.catalog -b image.fs cdisodir

The new way is to use cdboot file instead of boot floppy.
This will allow you to use kernel beyond 2880 kB.
To compile cdboot, run:
# cd /usr/src/sys/arch/i386/stand/cdboot ; make
This time we will not create a floppy image. We dont need it since we can use cdboot instead.
Put cdboot to your cdisodir.
# cp /usr/src/sys/arch/i386/stand/cdboot/cdboot cdisodir/
Copy over your kernel with rootfs inserted into it and second stage boot loader to your ISO directory.
# cp netbsd cdisodir/
# cp /boot cdisodir/
Create ISO image
# mkisofs -l -J -R -o livecd.iso -c boot.catalog -b cdboot -no-emul-boot cdisodir
Notice the -no-emul-boot option. It’s becouse the boot image is not an image of a floppy.

To check your ISO image, you can mount it as virtual device:
# vnconfig -v -c /dev/vnd0d livecd.iso
# mount -t cd9660 /dev/vnd0a /mnt
When you’re done:
# umount /mnt
# vnconfig -u vnd0d

Thats all, its done.

Special thanks to Yazzy

Nessus Ubuntu

Lets install Nessus in Ubuntu in a few steps

Open a terminal window and type in:

sudo apt-get install nessus

sudo apt-get install nessusd

sudo nessus-adduser

then add a user to nessus, set user and passwd, to login when ready.

sudo ln -fs /etc/init.d/nessusd /etc/rc2.d/S20nessusd

sudo /etc/init.d/nessusd start

sudo gedit /usr/share/applications/Nessus.desktop

Insert the following lines into the new file

[Desktop Entry]
Name=Nessus
Comment=Nessus
Exec=nessus
Icon=/usr/share/pixmaps/nessus.xpm
Terminal=false
Type=Application
Categories=Application;System;

After that you can find Nessus in the Gnome menu under Applications -> System Tools.

Y tu que hardware eres? :P

jejeje, me salio que soy el disipador de calor xD, aver chequen que harware son ustedes

para checar que hardware son den click aqui