mirror of
https://github.com/ElDavoo/wa-crypt-tools.git
synced 2026-04-26 06:05:51 +03:00
[GH-ISSUE #76] Enhance documentation #39
Labels
No labels
bug
documentation
enhancement
enhancement
good first issue
help wanted
info needed
invalid
low priority
pull-request
skill issue
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/wa-crypt-tools#39
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CanvaChen on GitHub (Jul 25, 2023).
Original GitHub issue: https://github.com/ElDavoo/wa-crypt-tools/issues/76
Originally assigned to: @ElDavoo on GitHub.
Hi, I’m interested in your project and I want to know how to generate message public key and message private key by myself. I know that these keys are usually stored in the axolotl.db file under the path /data/data/com.whatsapp/databases/, but I want to create them from scratch. Could you please explain the format and algorithm of these keys? Thank you.
@ElDavoo commented on GitHub (Aug 20, 2023):
This project does not to do anything with message keys and axolotl.db - although i agree that more documentation is needed
@ElDavoo commented on GitHub (Aug 20, 2023):
Auto generating keys will also be useful for #10 so it will be done at some point
@code-consensus commented on GitHub (Sep 11, 2024):
With regard to enhanced documentation, is it possible to add documentation on waguess ?
The main website only states "Hacky way to try decrypt backups", and running "waguess -h" just has the same description as wadecrypt (i.e. "Decrypts WhatsApp backup files encrypted with crypt12, 14 or 15").
What does this function actually do and how does one use it?
@ElDavoo commented on GitHub (Sep 11, 2024):
It does the same thing of wadecrypt, but in a more barbarian way: Takes the key and DB file "raw" and tries to guess where the key and the IV is. I left it there so if there is a new format we can't understand (but the underlying encryption stays the same) we might be good with it