Fixed ''backup_token' error during registration process #3127
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… info for idevice.
Open
|
Excuse me |
|
this error after use ios env |
|
@Rodrigosolari what command for yowsup-cli did you use? |
|
@gradol
|
i use echo command |
|
Nice and Work ...!!! many thank'....URAAAA !!! |
I got the same error here after trying to use "echo" demo. |
the solve |
|
Fixes #3120 |
|
This will probably not work for long, since WhatsApp introduced this // Android copy of Vesta proto. Ground truth here:
// - https://www.internalfb.com/code/fbsource/xplat/rust/vesta_client/proto/src/messages.proto
package whatsapp;
option java_package = "com.whatsapp.proto";
// Payload stored by successful registration (by `finish_register_request`).
message RegistrationPayload {
// The secret data to be protected by the HSM system.
// Holds serialized `WaBackupKeyData` proto.
optional bytes backup_key_data = 1;
// OPAQUE protocol third registration message.
optional bytes r3 = 2;
// Registration nonce.
// Deprecated and soon to be removed. Replaced by `transcript` (see protocol spec).
optional bytes opaque_challenge = 3;
// History of registration messages: `SHA256(R1, R2, opaque_challenge)`
optional bytes transcript = 4;
}
// Payload returned on successful account login (by `finish_login_request`).
message LoginPayload {
// `backup_key_data` from `RegistrationPayload` AES-GCM-128 encrypted with
// OPAQUE `shared_key`.
optional bytes backup_key_data_encrypted = 1;
// Nonce used for AES-GCM-128 encryption of `backup_key_data`.
optional bytes rk_nonce = 2;
}
// WA-specific proto serialized to/from Vesta `backup_key_data` field.
message WaBackupKeyData {
// User's backup key AES-GCM-128 encrypted with OPAQUE export key.
optional bytes aes_k = 1;
// Nonce used to AES-GCM-128 encrypt `aes_k`.
optional bytes k_nonce = 2;
}
As you can see the backup_key_data is said to be protected by a "HSM" system. |
vadetcka999
approved these changes
Jun 25, 2022
|
@Flam3rboy how did you extracted this proto file? |
|
@zek I just unzipped the apk and it was in the root dir |
|
@Flam3rboy wow I was looking for it in source code :D thanks |
|
I'm trying to send a message, but it doesn't come |
|
@vadetcka999 seems like you can't access WhatsApp <failure reason="405" location="frc" /> |
|
@Flam3rboy Now it looks like this. I did everything as in the commit and registration goes well, but with sending messages problems |
|
while trying this fix another error showing W 2022-07-29 21:25:40,370 yowsup.common.http.warequest - Passing Config to WARequest is deprecated, pass a YowProfile instead |
Whomakes
reviewed
Feb 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.