Aussie Telco Caught Handing Over User Mobile Numbers To Websites Without Consent
AlbanX writes: Australian telco Optus has been nabbed passing its customers' mobile phone numbers to third-party websites without the customers' knowledge or consent. The practice, known as HTTP header enrichment, aims to streamline the process of direct billing for customers, but they're not happy. The discovery was made by a user on the telco forum Whirlpool, and Optus confirmed it. They said, "Optus adds our customers' mobile number to the information in select circumstances where we have a commercial relationship with owners of particular websites."
...a crime was committed, or at minimum that we're going to actually do something to them.
Of course, we all know nothing will come of this, or at best a slap-on-the-wrist fine, which they've probably already calculated as a standard business expense.
Might as well just stop putting stories out like this until consumers are actually willing to act upon it. I'm willing to be there isn't enough consumer give-a-shit left in the world to tackle even this single issue, let alone tackle the mass arrogance that corporations pull off today at the expense of the customer.
What does it matter if you label someone as "caught" if the reaction is nothing.
See, this is exactly why I want a HTTPS web.
I do think Let's Encrypt is on the right track. When they show their protocol and open source software works. I'm pretty sure other CA's will follow.
Automating HTTPS deployment is a good thing.
Yes, the CA-system isn't a perfect system at all, but at least we are seeing some improvements in use of HTTPS:
- https://en.wikipedia.org/wiki/... (better revocation of certificates and faster loading of sites and better privacy)
- https://blog.mozilla.org/secur... (better revocation of certificates)
- https://en.wikipedia.org/wiki/... (old browser finally dying)
- HTTP/2 is faster than HTTP and sort of depends on HTTPS for backward compatibility for old proxy servers and public websites
- finally we are getting rid of all the old protocols like SSLv3 and get our server configurations cleaned up
Especially for regular visitors of a site things are improving:
https://developer.mozilla.org/... (a CA can NOT issue a cert for a fake certificate - works in Firefox and Chrome)
https://en.wikipedia.org/wiki/... (always HTTPS, no HTTP on the second visit)
New things are always on the horizon
I don't think we should cede the rhetorical battle by letting them call it "header enrichment."
I say we call it "tracking injection."
They can talk about 'trusted partners' and 'optimising websites' all they want, but the main point here is that they are sending your phone number over HTTP. Anyone on a hop along the way or of course the end website and their 'trusted partners' can now link an IP address to a phone number. Via other cookies they can tie that IP address to your previous ones and suddenly they have a Phone Number to go with the previously anonymous browsing history and customer profile.
Just imagine if that irritating banner ad could actually call you! It really is a phenomenal breach of privacy and security.
Dammit! I had a good one.
> "Optus adds our customers' mobile number to the information in select circumstances where we have a commercial relationship with owners of particular websites."
Someone needs to tell the weasel at Optus pushing this excuse that they have a COMMERCIAL RELATIONSHIP WITH THEIR CUSTOMERS TOO.