--- author: email: rafl@fsfe.org keyid: 742f2a428e635a5e name: Florian Ragwitz categories: - Hacking comments: [] date: 2006-04-01T01:36:27Z guid: 49a30f9e-45e2-4e5c-8517-734e7b936155 modified: 2006-04-01T01:36:27Z raw: "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1\n\n=pod\n\nAircrack, one my favourite wifi tools, was quite dead for a while. Bad\nenough, but after I\nL\nto the L driver recently I discovered that I\ncan't do injection anymore, which is quite bad. I searched for a workaround and\nfound L, a fork of aircrack, which has been\nmade recently. There weren't much\nL to the\naircrack codebase yet, but at least everything works well with madwifi-ng now.\n\nNow, as aircrack seems to be moving again I mplemented some changes I always\nwanted to have, such as\nL\n(L)\ninstead of attack numbers I could B remember and tried to get\nthem submitted to upstream.\n\nWhat I normally do that situation is to check out the latest development\nversion from the projects version control system, prepare a patch against it\nand send it to the development mailing-list afterwards. That's hardly possible\nwith aircrack-ng. Not only that one or two persons are having a master copy of\nthe code instead of using a nice, public accessibly version control system, but\nalso the total lack of mailing-lists or any other possibility to coordinate\ndevelopment besides an IRC channel and a wiki, which is only partially\neditable, makes contributing quite hard. After announcing some of my patches on\nIRC several times one of the upstream developers finally took a look at it and\nsaid he applied it so it'll be released in the near future.\n\nI'm happy about that, but the deficits in the development process still exist.\nTherefor I offered to sponsor hosting, including mailing-lists, a version\ncontrol system, a bug-tracking system and whatnot. It was thankfully declined\nas they already seem to have a hosting plan. Great! Unfortunately they don't\nhave the money for that currently, but they at least have plan. Hooray for\naircrack-ng..\n\n\nDebian packages for the latest release already exist and should be upload in\nthe next days, btw.\n\n=cut\n-----BEGIN PGP SIGNATURE-----\nVersion: GnuPG v1.4.6 (GNU/Linux)\n\niD8DBQFGCP+ndC8qQo5jWl4RAvAPAJ4+lUq7Nk86QqL0C2etjaiw5E3ndQCfUcdf\nQtfHH+KGPXPd89dp71ITRtQ=\n=QrSR\n-----END PGP SIGNATURE-----\n" signed: 1 summary: " Aircrack, one my favourite wifi tools, was quite dead …" tags: [] text: " Aircrack, one my favourite wifi tools, was quite dead for a while.\n Bad enough, but after I switched to the madwifi-ng driver recently I\n discovered that I can't do injection anymore, which is quite bad. I\n searched for a workaround and found aircrack-ng, a fork of aircrack,\n which has been made recently. There weren't much changes to the air-\n crack codebase yet, but at least everything works well with mad-\n wifi-ng now.\n\n Now, as aircrack seems to be moving again I mplemented some changes\n I always wanted to have, such as attack names (documentation patch)\n instead of attack numbers I could never remember and tried to get\n them submitted to upstream.\n\n What I normally do that situation is to check out the latest devel-\n opment version from the projects version control system, prepare a\n patch against it and send it to the development mailing-list after-\n wards. That's hardly possible with aircrack-ng. Not only that one or\n two persons are having a master copy of the code instead of using a\n nice, public accessibly version control system, but also the total\n lack of mailing-lists or any other possibility to coordinate devel-\n opment besides an IRC channel and a wiki, which is only partially\n editable, makes contributing quite hard. After announcing some of my\n patches on IRC several times one of the upstream developers finally\n took a look at it and said he applied it so it'll be released in the\n near future.\n\n I'm happy about that, but the deficits in the development process\n still exist. Therefor I offered to sponsor hosting, including mail-\n ing-lists, a version control system, a bug-tracking system and what-\n not. It was thankfully declined as they already seem to have a host-\n ing plan. Great! Unfortunately they don't have the money for that\n currently, but they at least have plan. Hooray for aircrack-ng..\n\n Debian packages for the latest release already exist and should be\n upload in the next days, btw.\n" title: aircrack-ng hacking type: pod uri: http://perldition.org/articles/aircrack-ng%20hacking.pod xhtml: "
\n

Aircrack, one my favourite wifi tools, was quite dead for a while. Bad\nenough, but after I\nswitched\nto the madwifi-ng driver recently I discovered that I\ncan't do injection anymore, which is quite bad. I searched for a workaround and\nfound aircrack-ng, a fork of aircrack, which has been\nmade recently. There weren't much\nchanges to the\naircrack codebase yet, but at least everything works well with madwifi-ng now.

\n

Now, as aircrack seems to be moving again I mplemented some changes I always\nwanted to have, such as\nattack names\n(documentation patch)\ninstead of attack numbers I could never remember and tried to get\nthem submitted to upstream.

\n

What I normally do that situation is to check out the latest development\nversion from the projects version control system, prepare a patch against it\nand send it to the development mailing-list afterwards. That's hardly possible\nwith aircrack-ng. Not only that one or two persons are having a master copy of\nthe code instead of using a nice, public accessibly version control system, but\nalso the total lack of mailing-lists or any other possibility to coordinate\ndevelopment besides an IRC channel and a wiki, which is only partially\neditable, makes contributing quite hard. After announcing some of my patches on\nIRC several times one of the upstream developers finally took a look at it and\nsaid he applied it so it'll be released in the near future.

\n

I'm happy about that, but the deficits in the development process still exist.\nTherefor I offered to sponsor hosting, including mailing-lists, a version\ncontrol system, a bug-tracking system and whatnot. It was thankfully declined\nas they already seem to have a hosting plan. Great! Unfortunately they don't\nhave the money for that currently, but they at least have plan. Hooray for\naircrack-ng..

\n\n\n\n

Debian packages for the latest release already exist and should be upload in\nthe next days, btw.

\n\n\n
"