@omkar072 you need to extract the img using whatever zip manager you use, i use mixplorer. inside /etc folder you will find the server.key. follow the explanation OP gave in his post GitHub - JFC-Group/AF-Customisation
-
Amazon Deals - ToS - Like us?
Reliance Jio AirFiber Root Access Guide
- Thread starter itsyourap
- Start date
- Featured
- Replies 310
- Views 37,655
@omkar072 Stop pinging @sammyXFR
Anyways, this is weird. The decryption somehow works totally fine in chroot but not on a normal setup!
This may be related to the fact that the OpenSSL version the router firmware uses is older:
The current (or the latest for Debian 12) seems to be:
Anyways, this is weird. The decryption somehow works totally fine in chroot but not on a normal setup!
This may be related to the fact that the OpenSSL version the router firmware uses is older:
Code:
/tmp # openssl version
OpenSSL 1.1.1s 1 Nov 2022The current (or the latest for Debian 12) seems to be:
Code:
$ openssl version
OpenSSL 3.0.14 4 Jun 2024 (Library: OpenSSL 3.0.14 4 Jun 2024)
but again jio is definitely making people fool. Sheezs and here we go installing older shit again
What it seems to be, the jump to OpenSSL 3.x from 1.1.x has a lot of newer security features, and is NOT backwards compatible.
So either, go get OpenSSL 1.1.1 binaries from somewhere, or build them on your own, or create a chroot with qemu-aarch64-static. Its actually quite easy given that you are already using binwalk to get the firmware extracted, but it makes it a bit harder for Windows users as they have to now use WSL.
So either, go get OpenSSL 1.1.1 binaries from somewhere, or build them on your own, or create a chroot with qemu-aarch64-static. Its actually quite easy given that you are already using binwalk to get the firmware extracted, but it makes it a bit harder for Windows users as they have to now use WSL.
Similar threads
