Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This just happened to me. I recieved messages (in gmail) from a contact that ware meant for his wife.

Be careful! I guess the best course of action is not to use gmail chat until google announces they have fixed the issue.



This tend to happen when your policy is to stop supporting tested, established protocols for chat clients and introducing your own in beta version to the entire planet at once.


No, trust has been broken.

You can't tell me you have confidence that this randomly won't happen again in the future? It's shattered mine.


Your search for perfect, flawless permanent security will be long, lonely and ultimately fruitless.

Already you've cut yourself off from flying, riding on trains and driving. Nobody can guarantee that deadly accidents will never happen, and indeed they do happen.

Presumably you only eat food your grow yourself. There are regular instances of contamination in the industrial food sector. Not that any guarantees can really be made, but at least contamination will be mostly your own fault.

See where I'm going with this?


I generally agree with this reasoning but this is not "flying", this is "flying with x airlines which dropped a plane once".

There are alternatives and one could choose a statistically safer one. There is obviously no guarantee. However, gtalk now has the highest likelihood of sending your messages to random people. That's a reason to avoid it.


When considering "passenger miles flown per incident", GTalk (and Google in general) has a security record completely on par with the best airlines.


What about the best chat services? In something like 18 years of chatting on the internet from IRC to ICQ, AIM, Skype, even Facebook messages, I have never seen a message go out to an incorrect recipient that wasn't the fault of my own negligence.


Well, they're also good[1]? British Airways didn't become a better airline when the Air France plane crashed, just like Air France didn't become a worse one.

1: Except, of course, IRC which is a protocol, not a service, and it was never designed to be private, but that's pedantry.


I think the overall point here is that the ability for a message addressed to one person to end up on someone else's screen carries some rather unfortunate implications for the internals of the service. Compare with IRC private messages, email, heck even XMPP.


Both IRC and XMPP cheerfully supports group messages?


I know XMPP does because I use that particular function at work daily, and IRC supports person to person PMs.

What I meant though is that the fact that whatever kind of shenanigans they're doing internally has a failure condition that can misroute messages is a bit scary.



Off course. I'll probably never use gmail chat for anything sensetive.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: