Re: [Announce] Aircrack-NG 1.1
 

Huh, auto-builder output:

[2011-05-25 21:42:03] Building iw 0.9.19-1maemo4 for target 'maemo-fremantle-armel-extras-devel'
[2011-05-25 21:42:48] OK
[2011-05-25 21:43:19] Building iw 0.9.19-1maemo4 for target 'maemo-fremantle-i386-extras-devel'
[2011-05-25 21:43:41] FAILED

Not sure if that means it'll put the armel version into the repository and skip the i386 version, or if it'll skip both now...

I just use the maemo extras assistant to upload that way. It let me do so just now, as you can see by the quoted output... if that's more convenient for you than the way you have been doing it then great - if not, then I don't know if any of the other ways would work.

Re: [Announce] Aircrack-NG 1.1
 

In the meantime, here's a link to download the .deb of iw that doesn't conflict with aircrack-ng. This is the exact same version as I just tried pushing into devel, but apparently that failed, so for now you have this. Remember, precompiled binaries dangerous etc etc. Use a condom, and such.

http://www.mediafire.com/?5kxpa7uobv69w5w

Re: [Announce] Aircrack-NG 1.1
 

Hello to all interested is there a way in which aircrack-ng can capture the data from channel 6

Re: [Announce] Aircrack-NG 1.1
 

Put wlan card into monitor mode.
Then run "airodump-ng --channel 6 [name of monitor mode interface, usually wlan0 or mon0]" as root. If you want to actually record the captured stuff, use the -w flag to give the main name of the file, and --output-format to specify what format to save the captured packets in.

"airodump-ng --help" is your friend. Also the aircrack-ng wiki.

For everyone else: My next plan with this package is adding a bugtracker field to the debian/control file (or wherever it's supposed to go), and then seeing if I can push it to extras-testing. Once there's a version down in -testing, I won't have to feel guilty about breaking the -devel version (well, before I didn't have to either, but it was easier to keep it working than explain to everyone how to get older versions of packages from the repository), and that means I can start experimenting with automatically installing to /opt/maemo/... and putting symlinks in the default path (/usr/[s]bin).

Re: [Announce] Aircrack-NG 1.1
 

@Mentalist Traceur....

can your aircrack 1.1 capture any access point with space in it???
old aircrack was unable to capture/injects any access point that have a space in it....

Re: [Announce] Aircrack-NG 1.1
 

i really doubt that. You can always put the mac id.

Re: [Announce] Aircrack-NG 1.1
 

Hmmm... Unless that changed between aircrack 1.0 and 1.1 upstream, I wouldn't think so. However, are you sure that was an actual bug, and not just, say, lack of proper formatting when inputting the name of the network when injecting? (Maybe putting it inside quotes and/or using a \ to escape the space from the shell? I'm not sure.) Keep in mind I'm not exactly an aircrack-ng suite expert. I just learned how to compile it after hawaii put me up to it, and then decided it wasn't very nice that people had to search various threads for pre-compiled .debs/binaries, or learn to compile for N900 themselves, just to get a more recent aircrack-ng version with more of the bells and whistles enabled.

Re: [Announce] Aircrack-NG 1.1
 

I bet this guy didn't try --help or know what a bssid is...
Just put the mac for the bssid.

Re: [Announce] Aircrack-NG 1.1
 

i use fAircrack v0.3 GUI along with aircrack-NG 1.1 on my phone...
that the reason why i ask about the space on the access point...
i know how to put the mac for bssid using x-term but i rather use fAircrack GUI cause is more simple to use...

Re: [Announce] Aircrack-NG 1.1
 

airodump-ng has never had the ability to filter via user-provided ESSID without this patch.

aireplay-ng doesn't use an ESSID to identify a network for non-authenticated frame transmission, but the BSSID and other values.

This is a PEBKAC error.

Re: [Announce] Aircrack-NG 1.1
 

Hi can anyone give a link to the old aircrack-ng 1.0-3.I think in the repository extras-devel or has been moved or deleted.With all due respect to the creator of the new version,but there is a problem with the data collection does not matter on which channel

Re: [Announce] Aircrack-NG 1.1
 

for me is working just fine aircrack-ng 1.1 with faircrack, for wep and wpa.

Re: [Announce] Aircrack-NG 1.1
 

I posted a fix for faircrack 0.3 here to address this issue:
http://talk.maemo.org/showpost.php?p...&postcount=749

Please help test this fix and report back.

Thanks

Re: [Announce] Aircrack-NG 1.1
 

Given that the other users don't seem to have any complaints, I suspect this is more specific to your device.

You're welcome to try with an earlier version, of course. ( http://maemo.org/packages/package_in...rack-ng/1.0-3/ )

Feel free to let us know if it works any differently than the current one for you.

hawaii: Do you know why the ESSID filtering patch that you linked to isn't incorporated into the upstream source? Is it that the developers haven't gotten around to it, or is there any actual issue with it?

Re: [Announce] Aircrack-NG 1.1
 

I have no idea why. It's a 9 month old submission, I've some issues on hold with Thomas that have yet to be pulled in either, but no big deal.

Re: [Announce] Aircrack-NG 1.1
 

K.

Well, I can start manually adding it to the aircrack-ng package I'm putting into the repository here for the time being, and then whenever it gets integrated upstream, great, less work for me again.

- Edit - Put 1.1-maemo5 in the autobuilder - this one should have a bugtracker link, the default CLI icon to indicate that it's a command-line package, and I changed the description to just list the names of all the included commands. Comments/questions/disagreements?

Re: [Announce] Aircrack-NG 1.1
 

Finally, 1.1-maemo5 has made it's way from the limbo packages sit in after being built successfully to the part where it actually hits the repository.

Re: [Announce] Aircrack-NG 1.1
 

I applied the patch hawaii linked to, and so 1.1-maemo6, now it the autobuilder, should come with airodump-ng capable of filtering by ESSID.

Unless something urgent requires fixing/updating, I'm not touching it for a few days, so that the 1.1-maemo6 version can clear the 10-day quarantine to be pushed into extras-testing.

Re: [Announce] Aircrack-NG 1.1
 

To my great regret as I assumed the old version is now in the past but anyway will experiment with new

Re: [Announce] Aircrack-NG 1.1
 

Okay, so today's update is:

My dpkg-buildpackage refuses to build the aircrack-ng suite if I keep the patch applied to airodump-ng (because it throws some warnings that my scratchbox's compiler apparently treats as errors). So until I figure out what flag to give dpkg-buildpackage, I'll have to unapply the patch to test locally, then apply it before making the source package to submit to the repository autobuilder, and repeat.

However, in the meantime, I'm pretty sure I have figured out how to automatically install to /opt/maemo/usr instead of /usr/local/ (it was infinitely more intuitive than I thought it would be). Which means, when I push the next update, you'll all have to change your symlinks if you have them already in-place. Then after that it's only a matter of time before I find out how to make symlinks get created upon install. And then no more symlinking to get the aircrack-ng commands inside your default PATH.

Re: [Announce] Aircrack-NG 1.1
 

Ok, I got optimization working perfectly on my device (edit: meaning, including the symlinking)... (postinst scripts ftw) now the question is why does maemo extras assistant give me file upload errors?

Re: [Announce] Aircrack-NG 1.1
 

I'd also recommend you scoot around in the aircrack-ng trac issues for other enhancement patches, although admittedly they have some open tickets that seem to have been resolved in svn, yet never closed.

Re: [Announce] Aircrack-NG 1.1
 

I'll look into it as time permits. "patch" throws some errors if you try to apply a .diff to a file that already includes those changes, so it shouldn't be too much of an issue if I ran into some that have been committed to SVN already.

In the meantime, everything sits and waits until the autobuilder starts... working, I guess. A brief glance at the thread of another program I use (Advanced Interface Switcher) suggests I'm not the only guy having issues getting the autobuilder to accept anything.

I also do want to get a version pushed to -testing - I felt properly working optification was good enough to warrant an upload, but after that gets uploaded, I want to prod it into -testing before changing anything else, then start on the other possible enhancements.

Also: did you have any specific enhancements in mind that you'd like to see pulled from there?

Re: [Announce] Aircrack-NG 1.1
 

Hi Mentalist, thanks for your good work.

I try to install this (iw_0.9.19-1maemo4) but HAM shows that is incompatible package. My N900 is with power47 + CSSU15. Would you please give me your idea about this issue ?! Thanks, :)

Re: [Announce] Aircrack-NG 1.1
 

Apologies if this has been mentioned already...

..but I keep getting "wi_write(): Illegal seek" from aireplay-ng

Is this a common problem?

Edit:
Just noticed the munged line above: "write failed: Network is down".

Guess it's just weak signal then.

Re: [Announce] Aircrack-NG 1.1
 

1.1-maemo7 has succeeded building in the autobuilder. Just a matter of time before it gets moved to the repo (might be a lot of time given autobuilder's bugs when I was last posting) Looks like it finished by the time I finished typing. I try to be diligent with the changelog, so you should be able to see what I changed last by viewing the aircrack-ng package's page by searching for it on maemo.org/packages.

But basically, this features optification+symlinking of all the binaries, and I fixed the descriptions slightly because I forgot to list some of the binaries that are included in the aircrack-ng suite when I updated the description last time.

Hopefully this also doesn't break anything that's already working.

Now, onto the issues:

shawwawa: Can you give any more details of what the error was? Or was that literally all that it said (if so, can you check the log from HAM. You can get to it from somewhere in the menu bar, I just don't remember exactly where in there...)? I know it's not power47 or the CSSU 15 installs that are to blame, because I have both of those installed too. It MIGHT be that iw isn't in a "user" section (when you use HAM, it only shows you programs that have "user" as one of its sections, the idea being to hide from the non-tech-savvy N900 users all the background libraries and other dependency stuff). So it's possible that HAM isn't allowing you to install the iw .deb because it's not a "user" package.

So you may have to install using "dpkg -i" (dpkg is the program for handling much of the .deb processing in Debian [and Ubuntu I think]; -i is the flag that tells dpkg to install the .deb file you're specifying), from the command line.

So open up X-Terminal, become root, and then cd to the directory you put the iw .deb file downloaded above, and then run "dpkg -i [name of .deb file]".

mr_jrt: It might actually not be a matter of network power/signal or whatever, but might be an internal aireplay-ng bug. I briefly looked it up, and it seems that in version 1.0 people were having this issue if they used the -B flag when running aireplay-ng. *Shrug* What command(s) exactly were giving you this error?

- Edit -

Frak, I have to put a prerm script into the package to get rid of the symlinks upon uninstall, don't I? Ugh. Looks like I have to upload another version already. (That's not to say it's a big deal - unless autobuilder messed something up, the package in the repo right now will still put everything where it needs to be, and symlink appropriately - it just won't automatically remove the symlinks if you wanted to uninstall - though it will remove the binaries and everything else).

Re: [Announce] Aircrack-NG 1.1
 

Put 1.1-maemo8 into the autobuilder. This includes prerm script for deleting the symlinks during uninstalling that the postinst script creates when installing, and fixes one (hopefully final) omission in the description. HOPEFULLY everything works and I don't have to touch it until I can get this version into -testing.

- Edit 2 -
Autobuilder finished building succesfully, so it'll be in the repo...soonish, hopefully.

Re: [Announce] Aircrack-NG 1.1
 

@Mentalist

Thank you very much for your detail descriptions. It works now !! I forget to use dpkg to handling such deb and I did recall that when I on the way home..... :) Thank you again for your great work on those awesome subjects.

Re: [Announce] Aircrack-NG 1.1
 

The command was:
Restarting the app immediately worked fine, and I think you're right - I don't recall the wifi status icon vanishing at any point.

Re: [Announce] Aircrack-NG 1.1
 

Those having issues with updating from 1.1-maemo7 to 1.1-maemo8, run this as root (you skip the second command if you haven't yet tried to update to 1.1-maemo8):

Sorry about that. It's the symlink thing I mentioned before: You have to delete the symlinks manually before updating because the current postinst script doesn't check if the symlink exists before making it, so it errors out if it tries to make one over one that already exists. This shouldn't be an issue from now on, because the prerm script included in 1.1-maemo8 should delete the symlinks correctly as it's removed before the next version installs. Also, I'll try to make the postinst/prerm scripts check if the symlink exists before making/removing it, so that this is even less likely to happen in the future.

Re: [Announce] Aircrack-NG 1.1
 

Okay, so I pushed 1.1-maemo9 to extras-devel, and autobuilder built succesfully, so that should be up soon. This SHOULD update without bugs from any version, regardless of previous symlinks/manually-placed-binaries, etc. That, or it'll break everything. :D If the latter, there's always next time.

Anyway, the only caveat is if you put your own aircrack-ng symlinks and/or binaries into /usr/(s)bin/, it won't override them at first - however, it will delete/override whatever is at those paths after the first uninstall/update. As I get better at understanding all this fancy code, I'll implement a mechanism similar to the one iDont used for busybox-power (his postinst/prerm scripts intelligently check the symlinks for if they are symlinks/binaries, and if they are symlinking to the busybox binary or somewhere else, and only override/delete the ones that are symlinks to the busybox binary).

But that's out of my skill level for now. But the good news is, other than extremely rare corner cases, you're not going to have any issues. IF my postinst/prerm scripts work right and I didn't make any errors.

Re: [Announce] Aircrack-NG 1.1
 

Ok, so apparently the repository as a whole is slow as hell, but I was finally able to update aircrack-ng through FApMan about 15 minutes ago, so it should be available for everyone.

And the update worked perfectly on my device. (From 1.1-maemo8 to 1.1-maemo9.)

If anyone has any other problems with it still, let me know.

Re: [Announce] Aircrack-NG 1.1
 

Thanks for all work which are you done

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

@disappear: No need to thank me (though I do appreciate it). I enjoy doing things that actually help other people, and this is something I can actually do to help.

- In related news -

Aircrack-NG 1.1-maemo9 is now in Extras-Testing. Rejoice, those who have -testing enabled, but not -devel.

Test, or if you've already tested, vote here, so that the masses with only Extras enabled may have aircrack-ng goodness too:
http://maemo.org/packages/package_in...ng/1.1-maemo9/
(It's not the most intuitive system - you need to log in with your maemo.org account, which is separate from your talk.maemo.org account, AND, you press the thumbs up/thumbs down icons to vote. So press the up thumb to vote for, press the down thumb to vote against.)

Here's the list of blockers which you should diligently check for before voting (I don't believe that this version violates any of them, as it has been optified, has a bugtracker link, and is otherwise awesome, but, if you genuinely believe aircrack-ng violates any of these, say so in here, so that I may look into fixing it):
http://wiki.maemo.org/Extras-testing...klist#Blockers

Also, the repository is being really weird. Last I looked, -devel armel was at 1.1-maemo9, as was -testing armel, BUT -devel i386 is still stuck on 1.1-maemo8, so there's nothing in -testing i386 for aircrack-ng.

This doesn't actually effect usability on the N900, because we see/use the armel versions on our devices, and the i386 version is just there...for some odd reason. But I'm worried that this is a symptom of some greater server-side issue.

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

Poop, I found one blocker myself. It doesn't explicitly state it's a command-line-only application. Version 1.1-maemo10 coming up, I guess.

- Edit -

Okay, version 1.1-maemo10 has been put into the autobuilder. This should be 100% clear of any of the blockers against it being promoted to Extras from -testing (as the only thing left was the description statement that it's command-line-only).

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

Okay, version 1.1-maemo10 has made it to -devel. Assuming the repository-side stuff doesn't glitch too much, 1.1-maemo10 should be making its way to -testing soon enough.

Anyway, once that makes its way to -testing, if no new issues are found (that aren't inherent to the upstream aircrack-ng suite as a whole), if we could get the ten votes needed to get it into extras, that'd be great. Normally I wouldn't push for enough votes immediately after getting this version down into -testing, BUT so many of us have used aircrack-ng while it's in -devel, that we know the package as a whole doesn't cause massive problems.

People have also ran 1.1 version compiles of aircrack-ng on their devices for a while aside from the in-repository version, and no major issues there.

And the changes I've made between 1.1-maemo1 and 1.1-maemo10, ultimately, have been mostly superficial changes to the debian/control file, such as changing the description/icon (don't break the package as we know), me changing the debian/rules to add the unstable and sqlite support (which people were doing to their 1.1 binaries for a while now) and to optify the binaries, and me adding scripts to add and/or remove the symlinks to the binaries.

The only thing that's relatively new is the scripts to create/remove symlinks, but if people don't notice issues with that pretty quickly, then that's not something that's likely to develop long-term bugs.

- Edit -
1.1-maemo10 is in extras-testing now too, if anyone's interested. And it looks like uploading the new version also un-stuck the i386 architecture files from the 1.1-maemo8 version, so now both armel and i386 architecture builds are in the repository in both -devel and -testing, as appropriate.

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

FRAK. Just found a typo in the prerm script that causes some symlinks to be left behind.

Thanks to the checking that my postinst script does it doesn't cause errors on uninstall/reinstall/update/whatever, but it's annoying,

I'll be pushing 1.1-maemo11 into -devel (and if the repository behaves well, into -testing; if it doesn't I'm going to sleep and only promoting to testing tomorrow) now. In the meantime, I'm not sure, but I MAY have hit upon some progress with pushing iw to the repos without an aircrack-ng conflict.

- Edit -
Uploaded to -devel.

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

Okay, it built in -devel, still waiting to be imported into the actual repository, near as I can tell.

However, a little bit of side-note on what I THINK is a success:
http://maemo.org/packages/view/iw/

I decided to cheat, and specified ONLY armel in the architecture field of the debian/control file, because last time iw built for armel but failed to build for i386. And it looks like that worked, and iw has succesfully gotten a new version for armel in the repository. This one should come without an aircrack-ng conflict.

...meanwhile still twiddling my thumbs waiting for the next version of aircrack-ng to make its way into the repository so I can download, test, promote to -testing, and go to bed.

- Edit -

1.1-maemo11 is in -devel, I just tested it and it creates and deletes symlinks perfectly. When installing/uninstalling/updating.

Now I'm going to promote this version into testing and I'm going to bed. When I wake up ~6 hours from now, I expect you all to have returned the love by testing and voting on the 1.1-maemo11 version once it gets to -testing.

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

So I finally got to manually check first hand, and I can confirm that the latest version of iw currently in the -devel repository is indeed one that does not conflict with aircrack-ng. I still don't like that I had to sacrifice the i386 build completely to push updates to it, but the old maintainer didn't answer my inquiries regarding how he got his sdk set up to actually work with the rules file in question... so yeah.

So anyway, next up on the list, now that iw doesn't conflict with aircrack-ng, is adding iw as a dependency of aircrack-ng (air airmon-ng depends on it for making mon0). So that will be up on the list for 1.1-maemo12. I'm still leaving 1.1-maemo11 in testing until that clears 10-day QA quarantine and gets enough votes, though, unless something needs fixing.

Re: [Announce] Aircrack-NG 1.1 (Now in Extras-Testing)
 

Thanks Mentalist. Great Job.