Lanux reunión aniversario

El grupo de usuarios de GNU/Linux de la ciudad de Lanús “LANUX”, lo invita a participar el sábado 5 de Noviembre próximo a su reunión mensual con charlas técnicas a realizarse en la sede de la Universidad Kennedy ubicada en la Av. Hipolito Yrigoyen 4651, Lanús. Jornada especial con motivo de los 20 años de Linux y los 10 años de formación
de nuestro LUG “LANUX”.

11:00 hs – Desayuno e introducción al Software Libre.

Charlas técnicas (12:00hs – 16:30hs):
Alta disponibilidad en GNU/Linux (Heartbeat+Pacemaker)

Cacheando contenido dinámico con SQUID y url-rewriters (SQUID/Grooveshark)

Cuevana LTA (Clonando Cuevana sin extensiones con HTML5)

Introducción a la telefonía IP con software libre (Asterisk VoIP)

Los esperamos!!

Lanux – Grupo de usuarios de GNU/Linux de Lanus
Visitanos en:


Algunas fotos de lo que fue la Reunión 🙂



Seguime :

El Indigena del año 2000

Dando vueltas encontré una revista de La Nación del día 26 de Agosto de 1973, donde le hacían una nota a mi Tía, Elena Cayuqueo, la nota vale la pena leerla, es ya de esa época como se veía la situación en esa época y como esperaba verla en el futuro.

Al final de las imágenes pongo un link para bajar la nota completa en PDF

Nota La Nacion 26 de Agosto de 1973 – El indigena del año 2000

Seguime :

V Mega Torneo a beneficio del Club Del Barman

En el día domingo 16 de Octubre de 2011 se realizo el Quinto Mega Torneo a Beneficio del Club Del Barman, como siempre la consigna es dar mas por los que menos tienen, hubo participantes de Mendoza, Venezuela, Uruguay, estuvo todo de 10!

Acá estoy en la recepción

Champy supervisando

La mise in place de Cocktail Tea

Mi trago se llamó nuevo mundo

2/10 Vecchio amaro del Capo

1/10 Parfait Amour Bols

4/10 Te de Coca

4/10 Ginger ale


Rodajas de jengibre con espirales de limón

salí segundo en la categoria

 Categoría Cocktail Tea:

Ya estaba casi por la mitad la copa :p pero la pude rescatar luego de la degustación

Mi trago se llamó Aire Citrico


4/10 Jugo de Mandarina

3/10 Cointreau

2/10 Mezcal

1/10 Strega


Espiral de mandarina

Categoría Clásico Profesional:

Categoría Wine Cup:

Algunas fotos :

Seguime :

Vuelve (parcialmente)

Después del grave problema de seguridad vuelve, aunque con cosas parciales, estuve bajando el código del Kernel últimamente de github, pero no es muy cómodo que digamos

aca un mail de recomendación para los desarrolladores del núcleo de la lista de correo de LKML (es bueno también como recomendación para tener en cuenta para todos los días en la computadora de casa)

The compromise of and related machines has made it clear that
some developers, at least, have had their systems penetrated.  As we
seek to secure our infrastructure, it is imperative that nobody falls
victim to the belief that it cannot happen to them.  We all need to
check our systems for intrusions.  Here are some helpful hints as
proposed by a number of developers on how to check to see if your Linux
machine might be infected with something:

0. One way to be sure that your system is not compromised is to simply
   do a clean install; we can all benefit from a new start sometimes.
   Before reinstalling any systems, though, consider following the steps
   below to learn if your system has been hit or not.

1. Install the chkrootkit package from your distro repository and see if it
   reports anything.  If your distro doesn't have the chkroot package,
   download it from:

   Another tool is the ossec-rootcheck tool which can be found at:

   And another one is the rkhunter program:
   [Note, this tool has the tendancy to give false-positives on some
   Debian boxes, please read /usr/share/doc/rkhunter/README.Debian.gz if
   you run this on a Debian machine]

2. Verify that your package signatures match what your package manager thinks
   they are.

   To do this on a rpm-based system, run the following command:
   	rpm --verify --all
   Please read the rpm man page for information on how to interpret the
   output of this command.

   To do this on a Debian based system, run the following bash snippet:
	dpkg -l \*|while read s n rest; do if [ "$s" == "ii" ]; then echo $n;
	fi; done > ~/tmp.txt
	for f in `cat ~/tmp.txt`; do debsums -s -a $f; done
   If you have a source-based system (Gentoo, LFS, etc.) you presumably
   know what you are doing already.

3. Verify that your packages are really signed with the distro's keys.

   Here's a bash snippet that can do this on a rpm based system to
   verify that the packages are signed with any key, not necessarily
   your distro's key.  That exercise is left for the reader:

	for package in `rpm -qa`; do
		sig=`rpm -q --qf '%{SIGPGP:pgpsig}\n' $package`
		if [ -z "$sig" ] ; then
			# check if there is a GPG key, not a PGP one
			sig=`rpm -q --qf '%{SIGGPG:pgpsig}\n' $package`
			if [ -z "$sig" ] ; then
				echo "$package does not have a signature!!!"
   Unfortunately there is no known way of verifying this on Debian-based

4. To replace a package that you find suspect, uninstall it and install
   it anew from your distro.  For example, if you want to reinstall the
   ssh daemon, you would do:
	$ /etc/init.d/sshd stop
	rpm -e openssh
	zypper install openssh	# for openSUSE based systems
	yum install openssh	# for Fedora based systems

   Ideally do this from a live cdrom boot, using the 'rpm --root' option
   to point rpm at the correct location.

5. From a liveCD environment, look for traces such as:
   a. Rogue startup scripts in /etc/rc*.d and equivalent directories.
   b. Strange directories in /usr/share that do not belong to a package.
      This can be checked on an rpm system with the following bash snippet:
	for file in `find /usr/share/`; do
		package=`rpm -qf -- ${file} | grep "is not owned"`
		if [ -n "$package" ] ; then
			echo "weird file ${file}, please check this out"
6. Look for mysterious log messages, such as:
   a. Unexpected logins in wtmp and /var/log/secure*, quite possibly
      from legitimate users from unexpected hosts.
   b. Any program trying to touch /dev/mem.
   c. References to strange (non-text) ssh version strings in
      /var/log/secure*.  These do not necessarily indicate *successful*
      breakins, but they indicate *attempted* breakins which means your
      system or IP address has been targeted.

7. If any of the above steps show possible signs of compromise, you
   should investigate further and identify the actual cause.  If it
   becomes clear that the system has indeed been compromised, you should
   certainly reinstall the system from the beginning, and change your
   credentials on all machines that this machine would have had access
   to, or which you connected to through this machine.  You will need
   to check your other systems carefully, and you should almost
   certainly notify the administrators of other systems to which you
   have access.

Finally, please note that these hints are not guaranteed to turn up
signs of a compromised systems.  There are a lot of attackers out there;
some of them are rather more sophisticated than others.  You should
always be on the alert for any sort of unexpected behavior from the
systems you work with.

Seguime :