The title is no longer required
I hope they reward him with an unlimited contract. It's the least they could do.
American T-Mobile subscribers can score free internet access by running traffic through a proxy with "speedtest" in its URL. Seventeen-year-old high school student Jacob Ajit found the loophole , since taken down, which allowed cheapskates to access T-Mobile's data network without paying. Ajit realised speed testing sites and …
Because it has been said that ISP's and mobile networks prioritise traffic to speed test sites to make their service look much faster than it actually is (and they want their customers to see full throttle). The fact that they allowed access to speed test sites free of charge shows that at least some tinkering is going on.
This post has been deleted by its author
As in your street cred, you mean ?
Come on, if nobody was getting hurt you had no pressure to publish, now did you ?
Responsible disclosure means you give the company a chance to react. If there is no hurt, you can give them even more time to react.
I discovered in late 2004 when on a prepaid SIM on Fido in Canada, that GPRS sessions routed over a "CONNECT" session on their WAP proxy were not charged for in their entirety (they charged an eye-watering 4c/KB = $40.96/MB with a 15c minimum charge - roaming on my Virgin Mobile SIM was a "mere" £5.12/MB even roaming on the same network) so only the minimum charge was levied. So, the obvious soluition was to set my SSH server to listen on port 443 and tunnel a connection to a Squid proxy over it.
This being GPRS over 2G, it wasn't fast. but 15c/session was certainly worth going for.
Unfortunately, they had "fixed" it by summer 2005 when I was next in Canada. I haven't been back since, but not because of that!
For the record, I tried this and it didn't work. I did it from a phone with a paid-up SIM but no data plan, which sounds like the same thing the teen hacker did, but of course it may not have been exactly the same plan. That was a couple days ago, but after I read another article about it of course, so perhaps it was already fixed.