*> Just another proof that the current scheme is broken.* The current scheme is not broken. It was intentionally designed the way it is for security purposes.
Thanks, Justin Anderson MagouyaWare Developer http://sites.google.com/site/magouyaware On Wed, Mar 9, 2011 at 11:48 PM, Nikolay Elenkov <[email protected]>wrote: > On Wed, Mar 9, 2011 at 11:32 AM, Pure J <[email protected]> wrote: > > I am doing an update on my application. I would like to sign it and > > publish > > However, when doing the process of jarsigner. It prompt me for the > > passphrase, unluckily , I forgot the passphrase. > > So, I would like to have some advice on it. > > > > 1) Is it possible to recovery/reset the passpharse of the keystore. > > Write a program to brute force it, start it and keep your fingers crossed > :) > > Someone already reverse-engineered it for your convenience: > > http://metastatic.org/source/JKS.html > > Might take some time, depending on how long your password was. > If you remember *exactly* how long it was, that would make things easier. > > Just another proof that the current scheme is broken. > (see the 'A Cautionary Tale: Backup your Keystore' thread) > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
