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

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex