Re: NeoPwn v2 = BackTrack Mobile!
 

First of all, appnss, thank you for posting some sense in this thread. I've really appreciated your past couple of comments.

Yes, and this is not something that has changed in the past couple of weeks. You didn't grow a family in 2 weeks, a handful of kids didn't ask for feeding in the past couple of weeks. Guess what, a lot of people here have jobs. I've been traveling the world and then some, yet I'm still following roughly what's what.

Again, if the amount of work is too big, ask for help. There are loads of people here who can help.

Wow wow wow; my moderator-hatted-me is going nuts on this. Don't give us that kind of bollocks mate. There may be people here who are just users, but I know that some of us definitely aren't. I can't speak for the vast majority of users in this thread, but how about you come to the next Maemo Summit (or whatever it's called these days) and have a look at the irc-fueled clique (we know who we are). Every single one of us has written code for Maemo, be it directly or indirectly.

Some are more involved than others, but the truth is, I think a lot of us have a lot more inside knowledge of how projects are managed, executed and written than you do, or even neopwn for that matter (from what we can tell).

Erhm, yes. On the neopwn.com front page. In the same post (or the one before) as the video teasers, it was indicated that a "a beta release of the first BackTrack Mobile operating system for the Nokia N900 [...] will be public shortly before the Blackhat and Defcon conferences in July 2010". This has now been conveniently removed from any of the posts -- shame that Google cache remembers.

http://img705.imageshack.us/img705/5...00729at065.png
(click on the image to go to the Google Cache)

No, he's crying like a small child, trying to find excuses so mummy wouldn't be mad because he broke her vase. 'Fess up. "Step up, or step aside". We're not asking for a finished project, we're asking for a release, no matter how finished. I don't care whether it's alpha and hangs if you stop turning around in counter-clockwise mode with a chicken leg dangling between your teeth. I just want something that shows where we're going, and how we can help.

Quite frankly, I (and I believe most people) don't give a shoot about the distribution. What I want is the driver. Without the driver (or some voodoo that allows for packet injection) the distribution (or any of the tools) is useless. It looks like crap, like script-kiddie-heaven-in-a-box.

As soon as this stuff is released (if it ever is), I'll work with MohammadAG in order to get the driver working without NeoPwn. Then, looking from the options we'll have, I'd like to see either a way to have injection working natively (without the chroot) and then port applications as we go further (and release progressively, in bite-sized chunks).

The last reason, I'm interested in BT Mobile, is that I am by trade a security expert. I have worked for many banks, governments, major telco companies, and I have a wealth of experience when it comes to encryption and penetration testing (check my Maemo or LinkedIn profile for further details).

And the last reason (bis), is that having fun with Bob from Widgets International at the airport is just the cheapest way to have fun, while waiting for delayed trains and flights these days.

Re: NeoPwn v2 = BackTrack Mobile!
 

Work loads change. What you are able to do, isn't necessarily exactly the same thing another person is able to do. You have no idea what might be going on in ones personal life.

Then I think it's quite obvious my post was not directed towards you in that regard. There's a reason I didn't say ALL or call specific people out. But I am sure you can agree, based on the type of posters and comments tossed around in the thread, most of the users simply want a "script-kiddie-heaven-in-a-box" and seem to have no quarrels with berating the developers as an attempt to guilt them.

The public beta will essentially have nothing of "real use to you" due to the fact that you seem to only want access to the patched wl12xx driver. Also, "shortly after" BH and DC doesn't mean before or during - which is what most people in this thread assumed, eluded to and then *****ed when no announcement was made within ONE day of BH starting.

Not all of the tools are wireless network testing suites. You do realize that? There are still a lot of packages that will work fine without requiring live frame injection drivers. I've built a lot of the tools that are on the roster for NeoPwn, running native in Maemo 5 or within a small chroot. If all you want is the patched driver, I can immediately think of 10+ people who would be willing to assist you for a fee, although the majority of them are at BH, DC and BSidesLV.

There's nothing needed to "get working without NeoPwn". The patch is a patch is a patch. Apply it to the source kernel, build the module and it will run inside and outside of the chroot. You could have done this, or contracted somebody like David to patch it for you. You didn't. You're waiting on somebody else to do the work. That's fine. But dictating how and when they need to have work done, when you aren't providing any real assistant - isn't fine.

Then you should offer up your assistance to the developer. I understand you may have a bad taste in your mouth, after this "fiasco" as many would like to call it, but the mere fact that you DO use these tools in your profession, should bring us all together to sort it.

Re: NeoPwn v2 = BackTrack Mobile!
 

Now I understand why you were so critic to people expressing their complaints:

It was not announced to be publicly beta released "shortly after" BH/DC (which could perfectly mean years after...) but shortly *BEFORE* BH/DC... and with big/bold remarks on the packet injection feature among many other great announcements posted on the site. And that was never even remotely questioned before the last possible day arrived.

The precise big words and announcements cached on google in the link crashanddie has posted, and many of us clearly remembered is the main reason for all the complaints. Nothing else.

Even if we assume that sometimes **** happens, does it seems now more logical and predictible the negative reaction?

Anyway, let's just hope that something positive can come out of this in the future...

Re: NeoPwn v2 = BackTrack Mobile!
 

You are quoting a post that clearly says BEFORE and u turn it into "shortly after". Nice :D

Re: NeoPwn v2 = BackTrack Mobile!
 

Which effectively means you can't prove it. Maybe you can assure us that it works, but then again, we only have your word for it. And in these troubled times, and taken into account the fact you have no reputation to speak of, your word is moot.

"Developed exclusively for Neopwn". What a sad, sad day this has become. Sorry excuse for open source.

So much for the "100% free download" we were promised, eh?

Re: NeoPwn v2 = BackTrack Mobile!
 

I have to agree with CrashanDie. As of now nothing has been released and Neopwn on N900 is just a proof of concept. Perhaps the target was too high to be reached. There is nothing bad with that. But, now, accept that and (simply) change how thing are being managed. Why not release a public downloadable alpha/beta/whatever? That's opensource after all, isnt't it?

Otherwise as someone stated already that's just vaporware. A good idea that took nowhere. Sad, but true.

Re: NeoPwn v2 = BackTrack Mobile!
 

Maybe the maker of the packet injection could be persuaded to part with the code for a little fee, as noepwn dosnt seems to be going anywere with all this gioing on.

Just remeber every1 has a price

Re: NeoPwn v2 = BackTrack Mobile!
 

maybe the dev isnt clear enough because he doesnt know what he wants

Re: NeoPwn v2 = BackTrack Mobile!
 

developed exclusively for NeoPwn?
IANAL but tell me, was here some line mentioning GPL somewhere in the headers of the code this exclusive work for NeoPwn was based on? Or do you actually claim you've written a new driver from scratch?

[confused]
jOERG

Re: NeoPwn v2 = BackTrack Mobile!
 

Then again, even with the GPL infringement, as long as there is no distribution of the binary, they're not forced to release the modifications.