![]() |
Re: Automatikwlan N900
its really interesting but for other wlans(not mine)its illegal or not?
really interesting what would happen if someone realizes that you are connected to his wlan. i mean. could this someone see my ip/imei and give it to the police?? |
Re: Automatikwlan N900
Do the kernel contain injection patch?
Dude it is GPL |
Re: Automatikwlan N900
It doesn't work over here... once you run the app, it says:
no se encontraron redes atacables (google translated: networks were not attackable) I can click on OK, then the app just closes... Anything that I missed? |
Re: Automatikwlan N900
Quote:
bump |
Re: Automatikwlan N900
Quote:
|
Re: Automatikwlan N900
Quote:
Also could you make an english version? |
Re: Automatikwlan N900
i think this app is limited only for certain access point, which probably only located in spain???
it was said that it works for wlan_xx and jazztel_xx (maybe those are the name of the access points? ) CMIIW |
Re: Automatikwlan N900
This thing makes my skin crawl. Closed source, secret kernel tampering, violating GPL left and right, all for potentially illegal purpose.
Should I mail you my credit card number directly, would that speed things up? |
Re: Automatikwlan N900
Quote:
Quote:
I works well, only tests in other areas Quote:
Quote:
exact, these are the names of access points Quote:
I do not understand anything, but in a few hours will put the source code Sorry for my English, I'm Spanish |
Re: Automatikwlan N900
OK, a friend asked me to jump into this thread, but there's really not much content to thrive on:
I've had access to the injection driver for quite some time. It was developed by an unknown person contracted by the guy who is behind NeoPwn. I haven't checked if the driver included in this package is the same as that driver, but considering that it showed up recently, after all the leaks surrounding the NeoPwn project, we can only assume that it is related. It's quite surprising that if indeed, My_PeSePe is the author of this GPL licensed driver, he did not start by releasing the source code. Also, they are going against the general Maemo guidelines that indicate that it is much more interesting for the community as a whole if application developers release their applications through the Maemo Builders (and hence the proper QA process enforced by the Maemo Extras repositories). What's even more surprising is that it would appear the author of the driver has violated his contract with NeoPwn. Be as it may, I'm quite sure this is better for the community, but still notable nonetheless. I will join MohammadAG in requesting the source code as soon as possible for this driver. I have been working on my own driver, based on my findings from reverse engineering the closed-source driver packaged with NeoPwn, but so far my progress has been difficult. I'm starting to get very tired of all these stupid pre-packaged so called hacking tools. Stop messing around and just post the drivers -- from there, people will be able to develop / port their own tools, and make real progress. I'm going to say the exact same thing that I told the NeoPwn lead: release public, and stop wasting everybody's time. You are bound by the GPL to release your source code. Please move towards this goal as soon as possible; I'm sure a lot of people will support you. |
All times are GMT. The time now is 12:39. |
vBulletin® Version 3.8.8