« previous next »
Pages: 1 ... 40 41 [42] 43 44 ... 62   Go Down

Author Topic: WhatsApp protocol  (Read 459179 times)

0 Members and 3 Guests are viewing this topic.

Offline Ducados

Re: WhatsApp protocol
« Reply #615 on: 30 07 2015, 15:56:13 »
I'm getting the message and seeing "[Ciphered message received]" instead of the actual message.

The contact gets single gray tick (not double) instead of blue double tick.

The console shows the same stuff I pasted this morning.

BTW, this started to happen after I updated WA client on the phone (Nokia C5-00). I fired the WA in the phone in order to force re-registration in Miranda and was forced to update to a new version.
« Last Edit: 30 07 2015, 16:19:40 by Ducados »
Logged
 

Offline Kajuru

Re: WhatsApp protocol
« Reply #616 on: 30 07 2015, 17:20:56 »
Same behaviour as before. Also no visual indication of encrypted message(using tabsrmm).
Registered and logged without ssl enabled, port 5222, if it makes any difference.
Logged
 

Offline Ducados

Re: WhatsApp protocol
« Reply #617 on: 30 07 2015, 18:45:40 »
Quote from: Kajuru link=topic=56.msg13561#msg13561and default date=1438276856
Same behaviour as before. Also no visual indication of encrypted message(using tabsrmm).
Registered and logged without ssl enabled, port 5222, if it makes any difference.

I use Scriver and I get everything as usual (time and name of the contact) but "[Ciphered message received]" instead of the actual text. I'm on SSL and default port, if it matters.
Logged
 

Offline Cassio

Re: WhatsApp protocol
« Reply #618 on: 30 07 2015, 19:32:44 »
Alright thanks, that ciphered text is supposed to show up.

2 more builds to try out.
The "retry" one notifies the WA server or other client to resend the message. No idea if that helps but i've seen it implemented recently in the pidgin plugin.
The "ressource" one uses a different account ressource for the connection (S60 instead of S40). This helped a few pidgin users as well.

If all this fails to help in any way (please give me feedback) apparently one must remove his WA account (unregister) completely and then register one's number freshly. The reason is that the WA server may have stored if you logged in with a encryption capable device before and thus defaults to that...
Logged
 

Offline Ducados

Re: WhatsApp protocol
« Reply #619 on: 30 07 2015, 20:05:31 »
I'm getting the messages perfectly OK with the ressource build. With the retry build I don't even get the encrypted messages (but can see the contact typing notification).
« Last Edit: 30 07 2015, 20:11:42 by Ducados »
Logged
 

Offline Cassio

Re: WhatsApp protocol
« Reply #620 on: 30 07 2015, 22:38:36 »
Okay too bad the other thing doesn't work. I guess there'll come the need to implement the lib axolotl in near future when these version work arounds stop working.

This is what I used as account ressource. Maybe someone could change it in the build?
Code: [Select]
#define ACCOUNT_RESOURCE  "S60-2.12.21"Edit: Something seems tobe wrong with this -> "unable to parse resource error" -> any ideas?

I don't have a matching user agent string and token for this, so maybe this may cause other issues with getting the password/registration at some point.
« Last Edit: 31 07 2015, 17:10:43 by Cassio »
Logged
 

Offline Kajuru

Re: WhatsApp protocol
« Reply #621 on: 30 07 2015, 22:43:31 »
Retry build got the notification of encryption that should have arrived in the build you posted earlier. Resource build is WORKING!!!! messages are coming inside <body></body> tags, not the <enc type> anymore.

Youre my hero!

Maybe if theres not much work to do, add the option to chose between s40 and s60 from gui?

On a side note, after about 2 mins, i got a server msg "unable to parse resource", even tho the plugin is still working.
Logged
 

Offline Ducados

Re: WhatsApp protocol
« Reply #622 on: 30 07 2015, 23:04:38 »
Quote from: Cassio on 30 07 2015, 22:38:36
This is what I used as account ressource. Maybe someone could change it in the build?
Code: [Select]
#define ACCOUNT_RESOURCE  "S60-2.12.21"
I don't have a matching user agent string and token for this, so maybe this may cause other issues with getting the password/registration at some point.

That's exactly the WA version my phone was upgraded to yesterday. It is indeed a Symbian S60 phone. Can  I help with the user agent string and token?

BTW, it is possible to hex edit such string in the dll and get stable working again?
« Last Edit: 30 07 2015, 23:06:39 by Ducados »
Logged
 

Offline Kajuru

Re: WhatsApp protocol
« Reply #623 on: 31 07 2015, 00:01:24 »
Im not receiving 100% of the messages, maybe around 90%, when i get the cant parse resource msg probably.

Also, since it could be a conflict coz I changed from a s40 to s60(miranda) without reregistering, i tried to request code: once it crashed, the second time it closed miranda silently. The silent closing bahaviour happens by itself too, about 2 or 3 times.

Going back to official dev builds:
Following the advice to delete my account on the official client in hopes it would forget i had a encryption enabled client... had to wait 5 hours before could re-register in miranda and now im getting <enc type="msg" v="2"> , unlike previously that i was getting v1.
« Last Edit: 31 07 2015, 08:13:04 by Kajuru »
Logged
 

Offline Ducados

Re: WhatsApp protocol
« Reply #624 on: 03 08 2015, 09:43:36 »
It looks like the message encryption setting is reversible.

Sick of Miranda crashing with the development platform, I reverted back to the stable version, whose WA plugin is dated 8/24, and I'm getting the messages OK. The logs shows that the message is not encrypted:

Quote
[11:35:13 F2674] [WhatsApp_1] XML received
<message from="cellnumber@s.whatsapp.net" id="id" notify="d" t="t" ty
pe="text">
<body>
No</body>
</message>
</ack>
Logged
 

Offline Kajuru

Re: WhatsApp protocol
« Reply #625 on: 04 08 2015, 22:25:37 »
Problem is that youre receiving the unencrypted messages, but not all.
I know for sure that, inside on single session(not closing message dialog), i get encrypted and plain text messages from the same contact. Im talking to person normally, after a couple minutes he asks why im not answering anymore, when i check log theres encrypted messages there.
Logged
 

Offline Eugene Muzychenko

  • Newbie
  • *
  • Posts: 9
  • Country: ru
Re: WhatsApp protocol
« Reply #626 on: 09 08 2015, 09:56:45 »
Tried to register on a fresh phone number - got the permanent "registration failed" and "old version" in the log.

Have created a ticket.
Logged
 

Offline Tobi

  • Newbie
  • *
  • Posts: 1
Re: WhatsApp protocol
« Reply #627 on: 09 08 2015, 11:04:07 »
I can't rgister a phone number as well. But I get a slightly different error ("status":"fail","reason":"no_routes"). I use Miranda-NG 0.95.4 # 13028 x64 and the Whatsapp Plugin Version 0.1.2.13. Full log at: http://pastebin.com/yN21bnrb

Any ideas what's wrong here?
Logged
 

Offline Cassio

Re: WhatsApp protocol
« Reply #628 on: 12 08 2015, 12:17:06 »
Just a minor thing but wouldn't hurt to patch this in:
Currently the features sent to the WA server on login do not correspond to what an official client sends.
This patch fixes that.

Logged
 

Offline Wishmaster

Re: WhatsApp protocol
« Reply #629 on: 12 08 2015, 21:43:03 »
Cassio: Committed, thanks:)
Logged
 
Pages: 1 ... 40 41 [42] 43 44 ... 62   Go Up
« previous next »