Fedora/RedHat

For those that were waiting for a faster way to transfer files via USB your ship has come in.  Laboratory Equipment wrote in their news that the USB 3.0 specification has been written and is now available for implementers.  The specification is available at http://www.usb.org/developers/docs/.  USB 3.0 has upped the transfer rate from 480 Mbps to 4.8Gbps and has optimized its power efficiency.

I, for one, can't wait to see these new devices on the street!

Wifitap baut auf scapy auf und erweitert die Möglichkeiten in einem WLAN-Netzwerk Angriffe auszuführen und ist ein Proof of Concept für Traffic Injection. Es erlaubt die Verbindung über ein offenes oder ein WEP-verschlüsseltes 802.11-Netzwerk ohne Anmeldung am Access Point durch Umgehen der Access Point-Beschränkungen wie MAC-Adressen-Filterung oder Stationsisolation.

Aktivieren des Adapters
# ifconfig ath0 up
Starten des Monitor Modes
# iwconfig ath0 mode monitor channel 1
Anlegen eines raw-Gerätes
# sysctl dev.ath0.rawdev=1
Starten des raw-Gerätes
# ifconfig ath0raw up
Die Benutzung von Wifitap
wifitap -b [-o ] [-i [-p] [-w [-k ]] [-d [-v]] [-h]-b Specifies BSSID in usual 6 hex digits MAC address format: 00:01:02:03:04:05
-o Specifies output Wifi interface for frames injection
-i Specifies input Wifi interface for frames sniffing
-p Used to tell Wifitap that input interface does not provides Prism headers
-w Activates WEP encryption/decryption with specified WEP key

The WEP key can be specified in the following formats:

• 0102030405 or 0102030405060708090a0b0c0d
• 01:02:03:04:05 or
• 01:02:03:04:05:06:07:08:09:0a:0b:0c:0d
• 0102-0304-05 or 0102-0304-0506-0708-090a-0b0c-0d

-k Specifies WEP key id, from 0 to 3
-d Activates debugging
-v Increases debugging verbosity
-h Help screen

Ein Liste mit weiteren Tools zum Beurteilen der WLAN-Sicherheit gibt es unter folgendem Link: http://www.wi-foo.com/index-3.html

Imaginemos que tenemos un archivo iso de una película DVD en nuestro disco duro y queremos reproducirlo mediante un reproductor de vídeo.

Para hacer esto vamos a necesitar el reproductor de vídeo mplayer . Por tanto lo instalamos

# yum install mplayer smplayer

Ahora supongamos que nuestra película en formato iso esta en /tmp/miPelicula.iso

Vamos a montar el archivo de nuestra película en un directorio mediante mount.

Para ello creamos un directorio como usuario normal:

$ mkdir directorioVacio

Nota: En realidad pudimos usar cualquier directorio que estuviera vació.

Y luego montamos el archivo iso de la película en el directorio que creamos (esto lo hacemos como root)

# mount -o loop /tmp/miPelicula.iso directorioVacio/

Finalmente mediante la linea de comandos y como usuario normal reproducimos nuestro dvd:

$ mplayer -dvd-device directorioVacio dvd://1-20

Este último comando le dice a mplayer que el directorio “directorioVacio” sera considerado como la ruta de un DVD. Los números 1-20 le dicen a mplayer que reprodusca las primeras 20 pistas (si el DVD tubiera menos pistas mplayer solo reproduciria hasta la última).

mplayer también tiene una interfaz gráfica llamada smplayer, con esta podemos iniciar la reproducción del directorio evitandonos el comando anterior.

Cuando terminemos de usar el directorioVacio debemos desmontarla:

# umount directorioVacio

Artículos Similares:

• Convirtiendo entre RPM, DEB, TAR.GZ con Alien
• Compartiendo ficheros con NFS.
• Amarok rockea tu música
• Error al actualizar fedora 9
• Gibibyte no es igual a Gigabyte

It may have been a whole 26 minutes since I last sang the praises of the Fedora Infrastructure team, but lo and behold, what should end up in my inbox but an uptime measurement survey from the good people at Pingdom. And guess who’s at the top of the heap?

I’d applaud but my hands are sore!

And as a reminder, our Infrastructure team uses only the tastiest free and open source software to do it like they do. Being free software is in the blood for these guys, and we love them for it. And of course, we owe a grateful shout out to our sponsors as well, who have deeded over equipment on which to keep the freedom coming.

Message sent to Egg today about Verified by Visa:
Dear Sir/Madam,

I would like to permanently opt out of "Verified By Visa" when making purchases online. It just moves the liability on to me and the technical implementation of it is frankly crap. If not, I'll cancel my card (I expect you'll be happy about that) since it's no longer useful for purchases.

If however you are going to introduce some scheme which is really secure, such as a hardware token or one-time credit card numbers or authorization by SMS message, then let me know.

A recent reports says Fedora Infrastructure is doing a good job :)

http://royal.pingdom.com/2008/11/19/linux-distros-and-apple-beat-microsofts-homepage-uptime/

0 downtime of our homepage in the span tested
2nd fastest home page load time (second only to Red Hat by 2ms)

Recently on the cobbler development branch several of us have been working to integrate power management features, among other things, for Cobbler 1.4. Patch activity has been huge lately and I'm enormously thankful for everyone involved.

Anyway, the idea is, since we're already handling all the low-level services needed for automated datacenter deployment and re-deployment (DNS, DHCP, TFTP, HTTP, syslog, etc) -- why not also do power management? It's easy.

You can read about this here: PowerManagement.

Shortly all of this will also be available to XMLRPC consumers of Cobbler, so I expect to see a lot more applications using it to provide install and low-level datacenter-management services.

The next feature to conquer is probably Roomba integration.

So! I have been working on GDB for a while now as part of the Archer project. Specifically C++ expression evaluation. More specifically lookup issues.

GDB has a lot of issues around namespace lookup a good chunk of which are hopefull fixed now in my branch.

Here are some issues that have been fixed:

namespace imports:

namespace A{   int x = 9; } int main(){   using namespace A;   x; } (gdb) break main ... (gdb) run ... (gdb) print x $1 = 9

namespace aliases:

namespace A{ int x = 9; } namespace B=A; int main(){ B::x; } (gdb) break main ... (gdb) run ... (gdb) print B::x $1 = 9

Imports if individual elements from namespaces:

namespace A{ int x = 9; int y = 99; } using A::x; int main(){ x; } (gdb) break main ... (gdb) run ... (gdb) print x $1 = 9 (gdb) print y No symbol "y" in current context.

If you want to try the above you can checkout the archer gdb branch:

git clone git://sourceware.org/git/archer.git

Then checkout my branch:

cd archer; git branch archer-swagiaal-using-directive origin/archer-swagiaal-using-directive; git checkout archer-swagiaal-using-directive

Next post I will talk about issues that I am still working on.

Toutes les distributions Linux ont aujourd’hui leur propre site Internet. On peut donc supposer qu’ils sont hébergés sur le même système d’exploitation, que celui dont ils font la promotion.

En partant de ce principe, Pingdom a réalisé une enquête pendant un mois pour savoir quels étaient les sites qui plantaient le moins souvent. Afin de rendre cette étude encore plus intéressant, ils ont décidé de rajouter ceux de Microsoft et d'Apple.

Et voici le résultat obtenu :



Apple s'en sort pas trop mal, par contre pour Microsoft c'est légèrement moins bien. On notera également que les distributions à base de Redhat (Fedora, Knoppix, CentOS...) sont en haut du podium avec moins de 2 minutes d'indisponibilité.

L'article complet est lisible ici :
royal.pingdom.com

Article original écrit par Sébastien Bilbeau et publié sur Tux-planet | ©Copyright - 2005 Toutes reproduction interdites.

Toutes les distributions Linux ont aujourd’hui leur propre site Internet. On peut donc supposer qu’ils sont hébergés sur le même système d’exploitation, que celui dont ils font la promotion.

En partant de ce principe, Pingdom a réalisé une enquête pendant un mois pour savoir quels étaient les sites qui plantaient le moins souvent. Afin de rendre le résultat encore plus intéressant, ils ont décidé de rajouter ceux de Microsoft et d’Apple.

Et voici le résultat obtenu :

Apple s’en sort pas trop mal, par contre pour Microsoft c’est légèrement moins bien. On notera également que les distributions à base de Redhat (Fedora, Knoppix, CentOS…) sont en haut du podium avec moins de 2 minutes d’indisponibilité.

L’article complet est lisible ici :
royal.pingdom.com

Article original écrit par Sébastien Bilbeau et publié sur Tux-planet | ©Copyright - 2005 Toutes reproduction interdites.

Here is the article link if you are an LWN subscriber:

http://lwn.net/Articles/307732/

If you're not an LWN subscriber, you can use this free link to get to the article:

http://lwn.net/SubscriberLink/307732/0efc7b75c5696ae5/

Please consider subscribing to LWN!

Still needs some work. Patch here. Pootle, kbabel, lokilizer are all on cards. Lets see where it reaches.

Note: Download and open in an desktop editor rather then checking in browser. Browser renders patch.

This morning I present some notes from Scott's excellent presentation at Sugar Camp today, about more effectively leveraging the work of other projects in Sugar. As a new full-time user of Sugar (day three!) these issues are especially acute for me, and I have a new appreciation for them.

Why did we choose Matchbox to run Sugar? Because (a) we cared chiefly about a full-screen windowing mode, and (b) Matchbox fit nicely into the small memory footprint on the XO, and (c) we didn't care about compatibility with legacy applications, because Sugar activities were going to RULE THE WORLD!

It's probably time to move beyond Matchbox, and it shouldn't be too difficult to do -- one of the nice things about the structure of X is that the window manager really is quite modularized. And the big new requirement, which Matchbox doesn't deal with well, is to deal gracefully with applications that really do need multiple windows. For instance: running Gimp would be truly nightmarish under Sugar, and would be very difficult to Sugarize. It would be mighty nice if such applications "degraded" gracefully.

Scott is looking at Awesome, which is a tiled window manager that also has a compatibility mode that allows for floating layers. There are other tiled window managers being considered; everyone's got their favorite, of course, but it does look like Awesome is in the lead right now.

We should also be using the standard notification, alert mechanisms, and system tray specs that freedesktop.org supports. (Seems like the only reason this hasn't been done so far has been time.) Here's what that means to me: when I use my IRC client in GNOME and someone says "hello gregdek," I get a glowing icon on my system tray. (Yaaay! Somebody likes me!) But XoIRC, right now, is incapable. Which makes IRC much less useful for me (although I'll probably get more done.) This is an opportunity to work directly with the folks at freedesktop.org, and this is important; if Sugar is to be viable, we must learn to work with other projects and take advantage of the work they've already done. What will these notifications look like in Sugar, exactly, which currently doesn't have a "system tray", per se? Unclear, but thankfully Eben is really good at solving these kinds of problems.

Finally, there is the question about the fundamental difference between "Sugar activities", which the current UI relies upon and expects, and "Linux applications", which the current UI completely ignores. As the real-world deployments grow, the need to consume non-Sugarized Linux applications grows with it. Having a window manager that handles this problem gracefully is only a first step: necessary, but not sufficient. Follow-on questions come up quickly. If Audacity isn't Sugarized, how do you even find it? Do you put a lightweight Sugar "launching" wrapper around Linux applications?

Seems like most of these things are making their way on the roadmap this week. That's a Good Thing. It's been a really productive session.

VPost finally delivered my very own Chumby. And I am pleased. I love the whole packaging. The box is a standard brown box and was really glad to see that the package was very environmentally friendly. There was one white styrofoamy bag that held everything but the rest was made from gunny sack materials. The chumby I bought was the latte model. Setting it up was a cinch and before long, I was able to watch David Letterman's Top Ten and his monologue along with a tonne of cool widgets. Apart from the Neuros OSD device I have, this is the second coolest tool worth my money.

Nice to see a good technical article about how RHEL clients can interoperate with MS AD. Thanks!

More than once after a photo shooting session I had the impulse to blog about how it went, the ups and downs, to echo my happiness or frustration. And usually I restrained myself from doing so, as I felt it will be useless noise in the various places places where it is aggregated - not a good thing to restrain yourself.

Of course I could use tags to filter the topics, but I don't want to be that restrictive and let from time to time some offtopic posts, so after some deliberation I decided to start a new blog, dedicated to photography (don't hurry up there, you won't find any upskirt photo), this way I can have a cleaner layout, a simpler navigation and a better URL.

With the launch of the new blog I did an important amount of preparation work: using scheduled post with a date in the past I populated the blog with photos from all those months since I have my current camera.

Of course I will still post photos here, but only when I think the subject is worthy. And, of course, the content on the new blog is also Free.

Congratulations, Matthew on being conferred the Entrepreneur Of the Year. These are the types of accolades that make a difference. What is more important is how open source (and a Red Hat subscription) changes how IT consumes technology and, in these turbulent times, crave out value to survive!

Mission

To configure a caching nameserver on a local machine which will cascade to another previously configured and functional nameserver (may or may not be caching. It'll generally be your ISP nameserver or the one provided by your organization).

Advantage

• Reduces the delay in domain name resolution drastically as the requests for frequently accessed websites are served from cache.

Working

• named gets a request for domain resolution.
• It checks whether the request can be satisfied from cache. If the answer is in cache and not stale, the request is satisfied from cache itself saving a lot of time :)
• If request can't be satisfied from cache, named queries the first parent. If it replies with the answer, then named will cache the response and subsequent requests for the same domain name will be satisfied from the cache.
• In case first parent fails to reply, named will query the second parent and so on.

(The working is my understanding of caching-nameserver using wireshark as traffic analysis tool and caching-nameserver may not behave exactly as explained above.)

How to install

named is by default on most of the systems by the package name 'caching-nameserver'. If its not present on your system, install using

[root@localhost ~]# yum install caching-nameserver [ENTER]

<!--break-->

How to configure

The main configuration file for named resides in /var/named/chroot/etc/named.caching-nameserver.conf which is also soft linked from /etc/named.caching-nameserver.conf . named configuration file supports C/C++ style comments.

For a caching nameserver which will cascade to another nameserver, there is nothing much to be configured. You need to configure "options" block. Below is a configuration file for a machine with IP address 172.17.8.64 cascading to two nameserver 192.168.36.204 and 192.168.36.210. The comments inline explain what each option does.

options { // Set the port to 53 which is standard port for DNS. // Add the IP address on which named will listen separated by semi-colons. // It'll be your own IP address. listen-on port 53 {127.0.0.1; 172.17.8.64;}; // These are default. Leave them as it is. directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; memstatistics-file "/var/named/data/named_mem_stats.txt"; // The machines which are allowed to query this nameserver. // Normally you'll allow only your machine. But you can allow other machines also. // The address should be separated by semi-colons. To allow a network 172.16.31.0/24, // the line would be // allow-query {localhost; 172.16.31.0/24; }; // Don't forget the semi-colons. allow-query { localhost; 172.17.8.64; }; recursion yes; // The parent nameservers. List all the nameserver which you can query. forwarders { 192.168.36.204; 192.168.36.210; }; forward first; }; logging { channel default_debug { file "data/named.run"; severity dynamic; }; }; zone "." IN { type hint; file "named.ca"; }; include "/etc/named.rfc1912.zones";

Start caching-nameserver

Now start the caching-nameserver using the following command

[root@localhost ~]# server named start [ENTER]

OR

[root@localhost ~]# /etc/init.d/named start [ENTER]

To make named start every time your reboot your machine use following command

[root@localhost ~]# chkconfig named on [ENTER]

Using caching-nameserver

To use your caching-nameserver, open /etc/resolv.conf file and add the following line

nameserver 127.0.0.1

Comment all other lines in the file, so that finally the file looks like

; generated by /sbin/dhclient-script #search wlan.iiit.ac.in #nameserver 192.168.36.204 #nameserver 192.168.36.210 nameserver 127.0.0.1

Now your system will use your own nameserver (in caching mode) for resolving all domain names. To test if your nameserver use the following command

[root@localhost ~]# dig fedora.co.in [ENTER]

Now if you use that command for the second time, the resolution time will be around 2-3 milli seconds while first time it would be around 400-700 milli seconds.

Example

Below is two subsequent runs of dig for fedora.co.in . Notice the Query time.

[root@bordeaux SPECS]# dig fedora.co.in ; <<>> DiG 9.4.2rc1 <<>> fedora.co.in ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7839 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;fedora.co.in. IN A ;; ANSWER SECTION: fedora.co.in. 83629 IN A 72.249.126.241 ;; AUTHORITY SECTION: fedora.co.in. 79709 IN NS ns.fedora.co.in. ;; ADDITIONAL SECTION: ns.fedora.co.in. 79709 IN A 72.249.126.241 ;; Query time: 531 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Nov 19 18:04:47 2008 ;; MSG SIZE rcvd: 79 [root@bordeaux SPECS]# dig fedora.co.in ; <<>> DiG 9.4.2rc1 <<>> fedora.co.in ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64233 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1 ;; QUESTION SECTION: ;fedora.co.in. IN A ;; ANSWER SECTION: fedora.co.in. 83625 IN A 72.249.126.241 ;; AUTHORITY SECTION: fedora.co.in. 79705 IN NS ns.fedora.co.in. ;; ADDITIONAL SECTION: ns.fedora.co.in. 79705 IN A 72.249.126.241 ;; Query time: 1 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Nov 19 18:04:51 2008 ;; MSG SIZE rcvd: 79 [root@bordeaux SPECS]#

If you are using clustered service with kerberos, you may want to merge hostnames keytab files to one for simple distribution.

• Create host and service principals.

kadmin: addprinc -randkey host/node1.corp.intranet.lan kadmin: addprinc -randkey host/node2.corp.intranet.lan kadmin: addprinc -randkey host/node3.corp.intranet.lan kadmin: addprinc -randkey host/node4.corp.intranet.lan kadmin: addprinc -randkey host/node5.corp.intranet.lan kadmin: addprinc -randkey host/node6.corp.intranet.lan kadmin: addprinc -randkey host/node7.corp.intranet.lan kadmin: addprinc -randkey host/node8.corp.intranet.lan kadmin: addprinc -randkey HTTP/node1.corp.intranet.lan kadmin: addprinc -randkey HTTP/node2.corp.intranet.lan kadmin: addprinc -randkey HTTP/node3.corp.intranet.lan kadmin: addprinc -randkey HTTP/node4.corp.intranet.lan kadmin: addprinc -randkey HTTP/node5.corp.intranet.lan kadmin: addprinc -randkey HTTP/node6.corp.intranet.lan kadmin: addprinc -randkey HTTP/node7.corp.intranet.lan kadmin: addprinc -randkey HTTP/node8.corp.intranet.lan

• Save them to only one file (cluster.keytab).

kadmin: ktadd -k /etc/httpd/cluster.keytab host/node1.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node2.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node3.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node4.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node5.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node6.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node7.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab host/node8.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node1.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node2.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node3.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node4.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node5.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node6.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node7.corp.intranet.lan kadmin: ktadd -k /etc/httpd/cluster.keytab HTTP/node8.corp.intranet.lan

• As alternative, you can use command ktutil if you already have a bunch of keytab files.

ktutil: rkt /etc/krb5/node1.corp.intranet.lan.keytab ktutil: rkt /etc/krb5/node2.corp.intranet.lan.keytab ktutil: rkt /etc/krb5/node3.corp.intranet.lan.keytab ktutil: rkt /etc/krb5/node4.corp.intranet.lan.keytab ktutil: rkt /etc/krb5/node5.corp.intranet.lan.keytab ktutil: rkt /etc/krb5/node6.corp.intranet.lan.keytab ktutil: rkt /etc/krb5/node7.corp.intranet.lan.keytab ktutil: wkt /etc/cluster.keytab

Voila.

Tanto OSOR.eu parriba y OSOR pabajo ni me había dado cuenta de que no había escrito nada sobre la huelga de informáticos. Aprovechando que no me la ha pedido nadie, he aquí mi opinión.

Estoy a favor de una huelga general del sector, porque nuestro sector es una mierda. Y esta cuestión forma parte de mi discurso habitual.

Estoy en contra de ésta huelga porque está convocada por los colegios de informática para los intereses de los colegios de informática, que ni son los mismos que los del sector ni, en mi opinión, de la mayoría de los que somos titulados informáticos.

Los colegios son un monopolio legal y llevo más de 10 años de actividad y resistencia contra toda clase de monopolios.

Realmente me encantaría poder ofrecer un análisis razonado de esta postura, pero las limitaciones de tiempo y mi escala de prioridades lo impiden de momento.