News for hackers. Stuff that matters.
Re:If you think O2 headers are bad, check this out. by mootothemax on Wednesday January 25, 2012 @06:28AM (#3509339)
This is not the fault of any one network; it's a fact of life when it comes to SMS. You can have all kinds of fun, whether it's messages that appear to be from you, your friend, or 11 characters of your choice, an SMS that will only display without being stored, or even a voicemail notification.

There's a nice guide to the format here:

http://www.dreamfabric.com/sms/

Re:If you think O2 headers are bad, check this out. by richardburton on Wednesday January 25, 2012 @06:37AM (#3509365)
Agreed. But they do not care at all. That is my complaint.
Re:If you think O2 headers are bad, check this out. by bad_user on Wednesday January 25, 2012 @07:03AM (#3509433)
To fix it, you'd have to reinvent the protocol.

That's like reinventing email. Well good luck with that ;)

Re:If you think O2 headers are bad, check this out. by richardburton on Wednesday January 25, 2012 @08:00AM (#3509551)
My lack of knowledge on this subject is evident here I am afraid. Is there not a way the networks could, like Google, try and detect spam or spoof messages?
Re:If you think O2 headers are bad, check this out. by bad_user on Wednesday January 25, 2012 @08:17AM (#3509587)
Yes it can with reasonable accuracy, but it's a whack-a-mole game, because there is no standard, many attempts have been gamed successfully by spammers, not all email servers are configured to use the latest "practices" (since this gets expensive) and not all email clients are configured to use the latest practices because that would trigger many false positives.

I just did an experiment.

Using my local Postfix email server with the default settings, I just sent an email from [email protected] to my GMail account. It arrived in my Inbox just fine. And I'm sure that if I sent this to dozens of people, then GMail would have flagged it, but it chose not to.

Re:If you think O2 headers are bad, check this out. by darklajid on Wednesday January 25, 2012 @08:11AM (#3509575)
Somewhere else in this discussion someone compared it to peering, which is quite a good example.

You grant (read: sell) permission to other people to deliver text messages to your subscribers. The very same way you get a text message from carrier A while being a subscriber of carrier B. Now enter international territory. You interconnect with lots of networks, each of which can (in my experience services like that were often from/cheapest in eastern Europe) hand out access to more people to send on their behalf.

Google can only try to protect you in limited cases. Check if the mail says it is originated from Google and notice that it isn't (flags a lot of false positives, if you are a valid sender, sending in a non-standard way). Checking headers (easily forged for most parts). Things like SPF [1] where you, as the admin of a domain, can tell the world that really only host X sends mails on your behalf.

The world might not care though - and the burden is again not on your very own 'carrier' (Google here), but on everyone on this planet that runs a domain.

There might be other ways, but inherently this problem is unsolved. Unless you went to a key signing party and verify that the data you got was signed by the key that you _know_ belongs to the sender (and you trust him not to give it away. And you trust him not to lose control of it or at least revoke it).

1: https://en.wikipedia.org/wiki/Sender_Policy_Framework

Re:If you think O2 headers are bad, check this out. by buster on Wednesday January 25, 2012 @09:08AM (#3509718)
Antispam solutions for SMS exist and are used afaik..