thegame_1980/KeyDive
1
0
Fork 0
mirror of https://github.com/hyugogirubato/KeyDive.git synced 2026-07-15 18:40:02 +02:00
Code Issues Packages Projects Releases Wiki Activity

release v3.0.0

Browse Source
This commit is contained in:
hyugogirubato
2025-06-09 18:12:49 +02:00
parent 2f74b4c5b7
commit 82d6a903dd
28 changed files with 5384 additions and 1620 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/advanced/CHALLENGE.md
+1 -1
View File
@@ -56,7 +56,7 @@ To extract unencrypted challenges using KeyDive and HTTP Toolkit, you can follow
6. **Use Extracted Data:**
- Use the extracted data with KeyDive by running:
```shell
keydive --device <DEVICE_ID> --challenge path/to/challenge
keydive --serial <DEVICE_ID> --challenge path/to/challenge
```
Replace `path/to/challenge` with the actual path to the extracted challenge data file.
docs/advanced/FUNCTIONS.md
+3 -3
View File
@@ -9,7 +9,7 @@ To utilize custom functions with KeyDive, particularly when extracting Widevine
Run KeyDive to detect the library path on the Android device:
```shell
keydive --device <DEVICE_ID>
keydive --serial <DEVICE_ID>
```
Replace `<DEVICE_ID>` with the ID of your Android device connected via ADB.
@@ -77,9 +77,9 @@ Ensure you have Ghidra installed on your system. If not, download it from the [G
Once you have the `functions.xml` file:
- Ensure KeyDive is set up according to its documentation.
- When running KeyDive, use the `--functions` argument to specify the path to your `functions.xml` file. For example:
- When running KeyDive, use the `--symbols` argument to specify the path to your `functions.xml` file. For example:
```shell
keydive --device <DEVICE_ID> --functions /path/to/functions_x86.xml
keydive --serial <DEVICE_ID> --symbols /path/to/functions_x86.xml
```
- Proceed with the key extraction process as detailed in KeyDive's usage instructions.