Archive for the ‘Uncategorized’ Category
Essential Java resources
January 27th, 2009
0 comments
Ted Neward, a consultant with ThoughtWorks and the principal of Neward & Associates, has published a list of libraries, tools and other resources – such as books, conferences or weblogs – any up-and-coming Java developer should have. The Java platform will be celebrating its 14th birthday soon, and it’s time to revise the story of one of most extended languages.
Link | Essential Java resources
Bash tricks
January 10th, 2009
0 comments
th3j0ker@alexandra:~$ echo hello hello th3j0ker@alexandra:~$ ^hello^bye^ echo bye bye
HDR time-lapse
June 19th, 2008
2 comments
This is a High Dynamic Range time-lapse from Goblins State Park in Utah (USA). It is very nice 
Amarok: Project Neon
May 6th, 2008
0 comments
Ladies and gentlemen, the doors are opened on the Neon project. Neon is no more than a new service by Amarok, which offers nightly builds to the users who want to try the lastest available version. It should be noted that is not a stable version, but it’s intended to be used by everyone who wants to help find bugs or to join development for Amarok.
If you are using Kubuntu Hardy Heron and you are interested on installing it, just add this line to /etc/apt/source.list and install the amarok-nightly package:
deb http://ppa.launchpad.net/project-neon/ubuntu hardy main
More information | Official Amarok site
Non-free SF on free systems
May 4th, 2008
22 comments
People are ignorant, but we already know that. As usual, I’ve read something really stupid on Twitter this morning. It said: I hope Apple will develop for everyone [every OS]. I think it would be one of the worst things to ever happen. Why do people want to install non-free software on free systems? If we want a truly free system, we cannot accept non-free software in our system. If people keep installing, running or developing non-free components, GNU/Linux will be turned into a fuzzy combination of free and non-free software. And we also could find free software which depends on non-free packages. The freedom movement would have failed if this happens.
People wants to install non-free software on free systems because they have not idea. They have not been educated using the free software principles. They don’t understand why the software should be free. They are confused between the free software and the open source movement. The universities doesn’t teach anything about the free software principles, even many teachers don’t know anything about free software. People wants to install non-free software on free systems because they don’t know what the free software is.
The insistence of running Adobe Photoshop on GNU/Linux is a good example of this. I’m not going to talk about the Photoshop/The Gimp challenge, although I manage well myself using The Gimp. Each user should know that Adobe Photoshop has a horrible license which it doesn’t allow the freedom to run, modify and redistribute it. The Gimp (GNU Image Manipulation Program) is available under the terms of the GNU General Public License (GPL), so we have the freedom to run, copy, change, study, distribute, improve the software and release our improvements. That’s how the community gets benefits. The Gimp, like free software, contributes to human knowledge, whilst Adobe Photoshop, like non-free software does not.
I read a message in a mailing list that could not have shocked me more. It said: Google also sponsored some work by Codeweavers to improve [Wine] support for Photoshop (’cause so many people want it) What a bad news for the free software! That’s not what people want, that’s not what GNU/Linux was made for. Why don’t Google support The Gimp instead of a Wine support for Adobe Photoshop?
Ubuntu on lettuces
April 6th, 2008
4 comments
I’ve seen on Entre tuxes y pepinos a curious lettuce with the Ubuntu Logo! The company is called El corral de los niños (The children’s farmyard) and it has been seen in Badajoz. And from what I have read, I would like to advise that it can contain bugs
The Mythical Man-Month
March 28th, 2008
4 comments
It’s obvious that a woman can create a baby in 9 months, but 9 women cannot create a baby in 1 month. This is the idea which The Mythical Man-Month wants to explain. If a job can be done by 5 men in 1 month, it’s said that this job requires 5 man-months. So applying simple arithmetic, would this project be completed in half the time if 10 men work on it? In the software development world, this thought is an outright fallacy. It’s not possible to multiply people by hours. The cost of a project is proportional to the man/months, but the progress is not.
Sometimes, assigning more people to a project to speed up the development is not the best idea, due to the time required to explain, learn, understand, mets, … about the project. Also we can find non-divisible tasks, so only one person can to do it. If we want to reduce the time, the way to do this is not by adding developers but discarding functionalities not implemented yet. For example, in DSDM we have the time and the resources fixed and the functionalities are variable (they depends on the fixed stuff).
The Mythical Man-Month is a chapter of a book called The Mythical Man-Month: Essays on Software Engineering written by Fred Brooks. This book was written 32 years ago, and it’s been one of the most transcendental books about software project management. It was republished as an anniversary edition in 1995 with the essay No Silver Bullet, where the author maintains the idea that there isn’t single development, in either technology or in management technique, that by itself promises even one order-of-magnitude improvement in productivity, in reliability or in simplicity. The main question is: Is it possible to develop without developers?
Ubuntu Hardy Heron Beta
March 21st, 2008
2 comments
The beta version of the latest Ubuntu, Hardy Heron 8.04, has been released. The official release will be on April 24th 2008.
Link | Ubuntu releases
Sacar claves WEP de redes Imagenio
March 14th, 2007
113 comments
Desde mi casa pillo sobre 5 o 6 redes con una ESSID de la forma WLAN_XX (donde XX son dos dígitos hexadecimales). Estas redes son típicas de los routers suministrados por Telefónica para Imagenio y ADSL. Las claves por defecto de estos dispositivos no son aleatorias, sino que siguen unas reglas para generarlas a partir del BSSID y el nombre del fabricante. Normalmente estos fabricantes son Xavy, Comtrend y Zyxel.
Vamos a realizar un experimento con una red que he pillado desde mi casa. Los datos que obtengo (y que vosotros podéis obtener fácilmente) son los siguientes:
Fabricante = Xavy
ESSID = WLAN_23
BSSID = 00:01:38:76:66:80
Con estos datos, y siguiendo las pautas de generación de claves de estos fabricantes podemos obtener los 7 primeros caracteres ASCII que componen la clave: X000138. La X viene a partir del nombre del fabricante Xavy, si fuese un router Comtrend comenzaría por C y si fuese Zyxel por Z. Los 6 caracteres siguientes podemos observar que se obtienen de la BSSID, que no es más que la dirección MAC del dispositivo.
Para realizar el experimento vamos a usar las siguientes herramientas:
- El suite Aircrack-ng Mother Edition
- El pequeño generador de diccionarios para este tipo de redes Wlandecrypter
Antes que nada, lo que debemos de hacer es capturar paquetes de dicha red. Esto lo podemos hacer con la herramienta airodump-ng del suite aircrack-ng. Con el siguiente comando le estamos indicando a airodump que capture los paquetes con la BSSID de la red que queremos obtener la clave WEP y los almacene en un fichero llamado captura.cap.
airodump-ng --bssid 00:01:38:76:66:80 -w captura eth1
Cabe decir que este comando requiere privilegios de root. Para aquellos que queráis experimentar y no pilléis señal de ninguna red WLAN_XX os subo el fichero .cap que genera la ejecución este comando (fichero cap).
Una vez capturados los paquetes en nuestro fichero captura.cap, prodeceremos a generar nuestro diccionario de posibles claves WEP usando wlandecrypter
wlandecrypter 00:01:38:76:66:80 WLAN_23 diccionario
Esto genera un fichero llamado diccionario que contiene las posibles claves WEP de la red WLAN. Ahora debemos de usar aircrack-ng para sacar la clave.
aircrack-ng -w diccionario captura.cap
Et voilà ! Contraseña WEP = X00013874F323 (ASCII) Dependiendo del número de paquetes que hayáis capturado (para estas claves no se necesitan demasiados) y de vuestra máquina en sí, el tiempo en encontrar la clave será menor o mayor. A mi me la calcula en tan solo 1 segundo.
