Live data from Hacker News

Reverse Engineering WhatsApp Web

github.com

111–120 of 127 posts

Re: Reverse Engineering WhatsApp Web

#111
From the GitHub readme:

> An UI that is not that technical, but rather starts to emulate the actual WhatsApp Web UI.

No, no, no. This trend of 'Phone UI' chat interfaces on desktop/laptop screens needs to stop. If you are going to all this effort to reverse engineer the protocol, at least make your front end customisable or at the very least IRCish in style.

Re: Reverse Engineering WhatsApp Web

#112
post #40

Earlier quoted context omitted.

It's Russian. You know, like: hand over the encryption keys or you, or someone you love will disappear.

Telegram is actually fighting the Russian government over the encryption keys, saying that it is impossible to hand them over (I assume this is for e2e encrypted secret chats). The consequence of this action is that they'll likely get banned (i.e. removed from app store). How much of this is a farce remains to be seen, since the whole nation, from casual users to small businesses to government employees use the app d…

I too appreciate nationalist sentiment, but the parent clearly stated: 'personal opinions also appreciated'.

But to be clear: I have a lot of distrust against governments regarding mass surveillance. But I distrust some governments more than others. And Russia is relatively high on that list for me. I think a healthy dose of distrust would be fitting for Russians citizens too.

Re: Reverse Engineering WhatsApp Web

#113
Have I missed something or is the only thing protecting the encryption scheme from impersonation of the phone the fact that the web-component's public key is (hopefully) never send to the WhatsApp servers?

The public key of the phone (the first 32 bytes of the variable "secret") is never authenticated by the web-component. Assuming they have the public key of the web-component, the WA Servers could hijack the whole scheme by sending their own public key in the "secret" instead of the phones. MITM doesn't seems possible though as the phone verifies the web-components public key by QR code.

I am no expert so, as I said, maybe I missed something, but relying on keeping a public key secret for security seems icky to me. Or maybe it's stupid to think about that too much, considering that both the phone-application and the servers including the Web API are closed-source anyway and will thus always remain icky security-wise.

Re: Reverse Engineering WhatsApp Web

#114
post #61

Earlier quoted context omitted.

Someone has to roll new crypto, otherwise we're stuck. That said, I know about the potential issues with Telegram's encryption.

You don't roll a new crypto and use it the day after, it must be tested for vulnerabilities, reviewed by expert cryptoanalysts. It can take years, much like a car has to be crash tested, a new crypto algorithm must go through a certain process to be considered good enough.

AFAIK WhatsApps crypto isn't too old either but that doesn't seem to prevent HNs resident cryptospecialists from recommending it.

That said: I belive them when they say that WhatsApps crypto is stronger.

On the other hand I would expect them to leave a little note somewhere about WhatsApp being a data collection tool for Facebook that also still happens to works as an instant messaging platform.

Re: Reverse Engineering WhatsApp Web

#115
post #83
post #26

Earlier quoted context omitted.

No, because it is a website.

They also have native apps on most mobile platforms (including Windows Phone, Blackberry and even Nokia Series 40). It isn't as easy to update all of them as one would think.

One of the things that has repeatedly pushed me off WhatsApp has been their very aggressive stance on this: I've several times stopped using it because "you need to update your app or this will all stop working in 7 days" and I've not been in the mood for jiggling the apps round on my tiny phone to be able to perform that update: the 7 days has passed, and I'm off WhatsApp again until such time as I "need" it.

Re: Reverse Engineering WhatsApp Web

#116

Earlier quoted context omitted.

That must've taken forever. Do you have any plans to reverse engineer other apps? I know people like you are in short supply and high demand.

It certainly did, but after all it was just a fun spare time project. I guess there would be a lot of interesting software to reverse engineer; I am always open to suggestions that are able to extend my knowledge. And well, if you mean it in context of a job... I don't have any experience regarding the job market yet, but that also sounds quite striking :)

I don't know much about the job market, I was talking about the internet in general. Too many applications are locked black boxes and reverse engineering them basically keeps them alive after their demise. However, not a lot of people actually put in the effort to reverse engineer this stuff, so keep up the good work for this stuff!

Re: Reverse Engineering WhatsApp Web

#117

I'm very hopeful this reverse engineering effort will enable the creation of a tool to export my conversations (WhatsApp can do email export, which let's be real, doesn't cut it for most cases). A point to those that support migrating to alternatives such as Signal. Signal is good, but far from great for a single reason: you need a phone number. This is very bad in necsec and reliability terms, my case: Reliability:…

Sounds like you could get a stable VoIP number and just use that. One time cost and has its uses for cheap long distance calling.

Most people expect you to have 1 mobile phone number, not separate ones for calling and messaging.

Re: Reverse Engineering WhatsApp Web

#119
post #5
post #2

Impressive work. Obviously, WhatsApp/Facebook would want to avoid a bunch of third party apps connecting to their service. How long until they make changes to make this more difficult/impossible?

If you have a web API it's impossible to secure it, especially when you have many platforms that access it ( web / mobile ect ... )

They "secure" it through legal force. Many startups are shut down by legal threats based on the CFAA, which effectively makes it illegal to talk to a server after you've been informed that you aren't allowed to do so (ordinarily, this information is conveyed through the Terms of Service -- a C&D is typical but not strictly required).

Re: Reverse Engineering WhatsApp Web

#120
post #8

Wow that's impressive. But I would imagine WhatsApp/Facebook can just change their protocol at any time since it is easy to redeploy a new version of the WhatsApp Web client, thus breaking any 3p clients built on the original protocol. That would require yet another reverse engineering effort that can take a while. And by the time its reverse engineered again, they can yet again change the protocol. So the only relia…

> it is easy to redeploy a new version of the WhatsApp Web client

You can choose your version when you send the requests

Post reply on HN