Skip to main content

Strong Password for KeyStore



I am developing android apps on my very personal computer.





Securing the keystore to sign android apps seems to me to be overkill. Securing is usally a pain, so I would apply it only when I get any realistic advantage. The android docs only talk about other users on the same computer, but that is not valid in my case.





Is there any rational need to secure a keystore on a secured personal machine?





Is there any rational need to use strong password on a keystore on a secured personal machine?


Comments

  1. If you can be sure, that no one, neither online nor offline, will ever be able to access your keystore file, then there is no need.

    ReplyDelete
  2. Yes there is a very real concern here.

    Lets say you get lucky and write a million dollar app. Malware distributers would only have to figure out who you are and hack your computer. Then they would have access to application source code and the keystore and mabye even your Google login credentials. If you haven't secured the keystore there is very little to stop them from distributing a hijacked version of your app through the android market through your account.

    Adding a password to the keystore really isn't that much extra effort and you should always do it.

    ReplyDelete

Post a Comment

Popular posts from this blog

Slow Android emulator

I have a 2.67 GHz Celeron processor, 1.21 GB of RAM on a x86 Windows XP Professional machine. My understanding is that the Android emulator should start fairly quickly on such a machine, but for me it does not. I have followed all instructions in setting up the IDE, SDKs, JDKs and such and have had some success in staring the emulator quickly but is very particulary. How can I, if possible, fix this problem?