Chat-API issue about wapi

[netfiretec]

Were you able to update the chat-api? call me on: Skype: netfiretec Telegram: [phone] Em dom., 21 de fev. de 2021 09:52, Ciclano <[email protected]> escreveu:

…

Ticket subject: Seu ticket foi aberto. Converse agora: https://direct.lc.chat/8505373/0 Powered by https://www.helpdesk.com/powered-by-helpdesk/?utm_source=ticket-footer-lc&utm_medium=email&utm_campaign=lc_8505373 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC7UHCMIODDUGZWLOQ7RZR3TAD6ZVANCNFSM4GJL4WDA> .

[ben221199]

Sure, I prefer Java, but maybe I could update my Python skills too. I already started on the WAPI Repo.

[ben221199]

No, my account is flagged for the second time this week.

[ben221199]

Oops

[ben221199]

My account is unflagged now.

[GM12Tick]

Flagged for what?

Btw, i think we should take the yowsup code base?

TGlal has made some work before.

[ben221199]

I don't know I'm flagged for. I think we should make a new code, but we can use code of yowsup and Chat-API for our project.

[GM12Tick]

Cool, what is the current state of the research?
Also, should this project be private? As per mpg message o agree that people may abuse it

[ben221199]

I know the following things:

• Every package begins with an int24 length.
• Since a certain version WhatsApp uses a tokenmap to compress the streamdata. This tokenmap depends on the version of the protocol.
• In protocol version 1.* they used RC4 to encrypt the messages to prevent stealing data.
• In protocol version 2.* they changed their encryption to Noise.
• A stream begins with a header. First the chars 'W' and 'A', then 2 bytes indicating the version.
• It looks like that there is a second header since 2.*: chars 'E' and 'D' and 2 bytes for the version. Than followed by a package with a size of 4 bytes and then the old WA-header.
• Registration process via v.whatsapp.net is also known.

Things to know:

• How does the encryption work?
• What does ED mean?
• What does the package between the headers mean?

If I forgot something, please tell me.

[GM12Tick]

I think that there were many changes wr probably need to reverse engineer the interesting parts.

you know reversing, right?

[ben221199]

Yes, we will see what is the best option.

[ben221199]

When I have some time, I will try things on my rooted phone.

[mosaw]

where is the project ?

[ben221199]

Is it not visible? I don't see a warning here.

[mosaw]

hi @ben221199
I fixed wart project to get the sms code and password
but I cannot login with the channle I have created , do u have a solution ?

[mosaw]

hey @ben221199 are u here !

[ben221199]

@mosaw Do you mean you succeeded in receiving a sms and used the code to receive the password, but that you cannot connect to the XMPP server with the password?

[mosaw]

yes excactly

[ben221199]

WhatsApp now uses FunXMPP 2.0 or later and this means that you cannot connect with the server with the current RC4 encryption. WhatsApp now uses Noise instead of RC4.

[mosaw]

so whats is the solution ?
how can i get instance

[ben221199]

We have to understand the new protocol of WhatsApp. Especially the Noise encryption.
Here is a full list of things we know and we need to know: #1 (comment)

[mosaw]

ok man thnx

[mosaw]

https://developers.facebook.com/docs/whatsapp

[ben221199]

That's the WhatsApp Business API. Also nice to have a look at, but our main goal is the normal WhatsApp.

[sebamenabar]

Hi @ben221199 @mosaw , are you still working on this? I'd like to contribute

[ben221199]

Sure... I have little time now, but when I have more, I certainly will continue. If you have information I can post, please send :)

[redrux]

@ben221199 Hello,

I can't see the repository and any code. But if you can publish we can contribute your repository.

[ben221199]

@ciclanoio Noise Protocol isn't implemented in the previous project. RC4 is the previous protocol and is implemented in the files: BinTreeNodeWriter and BinTreeNodeReader.

[netfiretec]

@ben221199 @GM12Tick Call me on Telegram or Skype, maybe we can make this a reality for both of you, my project is quite advanced, including the nois protocol implemented.

Skype: netfiretec
Telegram: https://t.me/LeandroDeFranca

[ciclanoio]

## Seu ticket foi aberto. ## Ticket subject: Re: [ben221199/WAPI] Chat-API issue (#1)

…

---- Autor: NetFire tec Data: Wed, 08/19/20 4:35 pm Mensagem: @ben221199 @GM12Tick Call me on Telegram or Skype, maybe we can make this a reality for both of you, my project is quite advanced, including the nois protocol implemented. Skype: netfiretec Telegram: https://t.me/LeandroDeFranca

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1 (comment) Converse agora: https://direct.lc.chat/8505373/0 Powered by https://www.helpdesk.com/powered-by-helpdesk/?utm_source=ticket-footer-lc&utm_medium=email&utm_campaign=lc_8505373

[ben221199]

At the moment I'm implementing a client in Java. Registration is done using yowsup. When connecting to the communication server, I send the WhatsApp header, then I start the Noise protocol handshake using protobuf segments. I first send a ClientHello, I receive a ServerHello with NoiseCertificate data and then I send a ClientFinish with ClientPayload data. However, after that segment, I don't receive anything, so that is strange. The Noise implementation I'm using (rweather/noise-java#1) gives some weird errors when verifying the MAC, but when I disable this verification, the library works fine. This errors also occur when I don't communicate with the WhatsApp server, but with my own server that uses the same library. However, after the handshake with my own server, I receive data that my server sends, but when connecting with the WhatsApp server, as I said, I don't receive anything. Maybe there are some tiny differences between normal Noise protocol and WhatsApp noise protocol.

[ciclanoio]

## Seu ticket foi aberto. ## Ticket subject: Re: [ben221199/WAPI] Chat-API issue (#1)

…

---- Autor: Ben Data: Mon, 01/04/21 7:33 am Mensagem: At the moment I&#x27;m implementing a client in Java. Registration is done using yowsup. When connecting to the communication server, I send the WhatsApp header, then I start the Noise protocol handshake using protobuf segments. I first send a &#x60;ClientHello&#x60;, I receive a &#x60;ServerHello&#x60; with &#x60;NoiseCertificate&#x60; data and then I send a &#x60;ClientFinish&#x60; with &#x60;ClientPayload&#x60; data. However, after that segment, I don&#x27;t receive anything, so that is strange. The Noise implementation I&#x27;m using (rweather/noise-java#1) gives some weird errors when verifying the MAC, but when I disable this verification, the library works fine. This errors also occur when I don&#x27;t communicate with the WhatsApp server, but with my own server that uses the same library. However, after the handshake with my own server, I receive data that my server sends, but when connecting with the WhatsApp server, as I said, I don&#x27;t receive anything. Maybe there are some tiny differences between normal Noise protocol and WhatsApp noise protocol.

-- You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub: #1 (comment) Converse agora: https://direct.lc.chat/8505373/0 Powered by https://www.helpdesk.com/powered-by-helpdesk/?utm_source=ticket-footer-lc&utm_medium=email&utm_campaign=lc_8505373

[ben221199]

I will close this issue, because there is now code in the repository. Registration is implemented. Also Noise protocol and FunXMPP converter is implemented. The things that should be done now, like End-to-End encryption and messaging, aren't relevant to this issue.

[ciclanoio]

Ticket subject: Seu ticket foi aberto. Converse agora: https://direct.lc.chat/8505373/0 Powered by https://www.helpdesk.com/powered-by-helpdesk/?utm_source=ticket-footer-lc&utm_medium=email&utm_campaign=lc_8505373