181–186 of 186 posts
Earlier quoted context omitted.
How about you use proper HTML instead of just the frame code and nothing else? e.g.
Also will be interesting to check other ways: 2767 3855%23">, 2767 3855%23">, location.href="tel: 2767 3855%23"; and so on.
http://pastebin.com/cGgs7T4h << some thoughts
I created an Android app to intercept these requests and prevent them. https://dl.dropbox.com/s/28lk6rn09x84qqg/AutoResetBlocker.ap... Please test it and make sure it works for you. 1. Open the above link on your phone 2. Install the application (it requires no special permissions) 3. Try this IMEI test: http://jsfiddle.net/kKFn8/ 4. Check the box to make "Auto-Reset Blocker" the default action 5. Auto-Reset Blocker…
Thanks, works as intended on my S3. Any chance of releasing the source code though?
Earlier quoted context omitted.
Considering a CTCP request is just a PRIVMSG with ^A wrapped around the "command word", and a CTCP reply is just a NOTICE with the same ^A thing, you can make them "say" just about anything. It's unclear why an IRC client would need to worry about "escaping" +++, except if it's specifically been designed for people with bad modems. Those of us with good modems back in the dialup days just laughed at this insanity. Ha…
Sorry, I should have been more clear. The modem could also guard the sequence by requiring interstitial pauses, but I believe this was patented by Hayes in the 80s.
Here's a safe version of the exploit that displays your IMEI: http://kristofferR.com/samsung.html Check the html in your desktop browser first, for all you know I might as well be a malicious douchebag. The exploit seems to require a stock Samsung Galaxy dialer, works fine on my cheap Samsung Galaxy Y but not on my friend's modded S3 with a vanilla Android dialer.
Displayed my IMEI on an HTC Legend circa 2010, with Cyanogen 7.1, just to add to the data.