I forgot the key password, thinking about finding Brutus Force. will it ruin the keystore?

I recently realized that I lost the password for my keystore (or maybe the keystore is somehow corrupted)

It keeps giving me an error: wrong password or wrong password

I created a (completely non-optimized) algorithm for the Brute-Force password, allowing it to work all night. However, I'm not sure how many failed password attempts will block the keystore.

Does anyone know something like this?

UPDATE
The algorithm I developed works fine (I use Java), but I realized that usually the Keystore tool asks for a password only when I press enter. but in order to make brute force work, I would like her to have a switch and accept the password on the same line. is it possible?

+12
android brute-force keystore
May 27 '11 at 8:12
source share
4 answers

Share my experience after everything is available.

1- The attack using the smart word from android-keystore-password-recover is what ultimately worked for me after spending a day trying a different list. Unfortunately, it does not support multithreading, and I could not get it to work faster than 30,000 samples / sec. I can contribute multi-threaded support to the project soon.

2- KeystoreBrute was the best for brute force attack at 320,000 samples / second. However, if you make numbers, it will take 3.5 days for a password of 6 characters and 177 days for 7 characters.

3 If you only need to crack the keystore password, but not the certificate password (also called an alias password), this tool will simply change it for you.

Good luck

+26
Apr 25 '13 at 17:43
source share

The number of password attempts will not damage the key.

I had the same problem. I solved the problem by creating my own key-drag and drop application.

here is a link to the github repository for this code.

https://github.com/volure/keystoreBrute

Anyone on the planet can use this or add to it.

This works based on password segments.

My password was like

Foo @ 543Pass

so I added all possible segments

Foo Foo FOO

etc. Then he ran through the objects like an odometer.

Its rough code, but hardcoded to work up to 5 segments.

My attempt was successful. Hope you too.

+10
Sep 15 2018-11-11T00:
source share

No, brutal forcing will not ruin the keystore. However, it is worth noting that if you try to guess the password manually using the Android Studio or Eclipse wizards, even if you enter the wrong password, even once, it continues to talk about the following attempts: "Keystore forged or the wrong password", even if you entered the correct one password. To work around this, simply close and reopen the wizard.

PS If you have a question that you forgot the password of your keystore, you can try the steps mentioned in the password recovery guide for the Android keystore .

+2
Jul 24 '16 at 11:57
source share

You do not need to use any key recovery method and password, since it takes many days to recover some time when it does not work, so you need to replace the keystore with a new keystore, you do not need to remove the application from the play store without removing apk You can upgrade your apk with a new keystore file. Now it’s possible. After May 2017, you can update the application if you have lost your keystore or key store password. Do not lose hope that you can update your application with the new Keystore file, please refer to this http://geekcodehub.com/blog/ new Keystore certificate update on the playstore . Here I wrote how to update apk, if you have lost the keystore, follow the step and create a new keystore, I updated my application using this step. you need to enable Google Play subscription to enter the console of the playback console.

0
Sep 29 '17 at 5:38 on
source share



All Articles