Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Security Bug Communications Encryption The Courts IT

WhatsApp Threatens Developers of PC Gateway With Legal Action 27

An anonymous reader writes "In an apparent reaction to the security vulnerabilities demonstrated by The H's associates at heise Security, the company behind WhatsApp Messenger is taking action against the developers of a library of functions for using the WhatsApp service via a PC. The developers have responded by removing the source code from the web. However, the popular texting alternative WhatsApp still has a major security problem. Attackers can compromise other users' accounts with relative ease, and send and receive messages from another user's account. Forked versions of the code are still available on Github."
This discussion has been archived. No new comments can be posted.

WhatsApp Threatens Developers of PC Gateway With Legal Action

Comments Filter:
  • I remember them! (Score:5, Interesting)

    by TheSpoom ( 715771 ) <{ten.00mrebu} {ta} {todhsals}> on Wednesday September 26, 2012 @04:09PM (#41468547) Homepage Journal

    One of our clients wanted us to send notification messages over WhatsApp to end users, but they don't have an API and at the time, this third party library was not available. We told them we couldn't do it. Sounds like we avoided a shitstorm.

  • by idontgno ( 624372 ) on Wednesday September 26, 2012 @04:19PM (#41468707) Journal

    From a business ("risk management") perspective, it often costs no more to offload liability or otherwise mitigate the impacts of a security event than to actively prevent the security event. In that case, is anyone surprised a business makes a business decision? If you ask the business, security features support the business and not the other way around, so business priorities always take precedence.

    And yeah, that means that if there's a breach, if you can decrease the overall cost of notification and settlement with the victims, letting the breach happen may be the more business-savvy choice.

    Sucks, but that's the profit motive for you.

  • Bunch of crackpots (Score:4, Interesting)

    by DMiax ( 915735 ) on Wednesday September 26, 2012 @04:52PM (#41469215)

    Few developers make me so angry as WhatsApp's ones. They just took XMPP, made a couple of changes so that it does not work with normal clients, forgot about any kind of security and call it a day. Their biggest idea is using phone numbers as identifiers and marketing their app as an SMS replacement instead of an internet chat. Fuck them.

  • by Nerdfest ( 867930 ) on Wednesday September 26, 2012 @05:49PM (#41470021)

    Apple did the same thing.

  • by Anonymous Coward on Wednesday September 26, 2012 @07:30PM (#41471099)

    Few developers make me so angry as WhatsApp's ones. They just took XMPP, made a couple of changes so that it does not work with normal clients, forgot about any kind of security and call it a day. Their biggest idea is using phone numbers as identifiers and marketing their app as an SMS replacement instead of an internet chat. Fuck them.

    Yeah, the big thing about it is using phone numbers as identifiers. But even that doesn't justify the security holes. They could just generate a random key and store it on the server and on the device. So, the phone number would be the "username", the random key would be the "password". If the user changed device, the current SMS verification can be used to verify the user is really using the same phone number, and then issue a key regeneration. There is no excuse to use some predictable number based on public info like IMEI, MAC adresses etc.

"Here's something to think about: How come you never see a headline like `Psychic Wins Lottery.'" -- Comedian Jay Leno

Working...