Actually the instructions state you should use 25+ years for a single
application; more if you sign multiple applications (there's a 20 year
minimum for app on Google Play)
If you encounter this issue in 25 years, post it on their
future-holodeck-message-board :-) I think the idea behind this
On 07/22/2013 12:08 AM, Ted Hopp wrote:
On Thursday, June 14, 2012 12:43:51 PM UTC-4, Dianne Hackborn wrote:
The platform has an app signed with a cert. If you want to
install an update to that app under a different cert, how could
the platform trust that this is actually coming
On Thursday, June 14, 2012 12:43:51 PM UTC-4, Dianne Hackborn wrote:
The platform has an app signed with a cert. If you want to install an
update to that app under a different cert, how could the platform trust
that this is actually coming from the author who owns the original cert
On Mon, Jul 22, 2013 at 1:08 PM, Ted Hopp ted.h...@gmail.com wrote:
On Thursday, June 14, 2012 12:43:51 PM UTC-4, Dianne Hackborn wrote:
The platform has an app signed with a cert. If you want to install an
update to that app under a different cert, how could the platform trust that
this is
Actually, you should have a fall back plan. It's easy to backup your key.
On Thu, Jun 14, 2012 at 11:35 AM, Saurav to.saurav.mukher...@gmail.comwrote:
Thanks Mark.
You have always helped me out, now and in the past!
I know that the encryption is irreversible, wanted to know if there is a
Thank you so much Dianne and Others for your quick and strong response.
I don't know whether any of you did not get the point that I know it was
my mistake, to lose the keystore file. No doubt on that :)
Anyways, as you all said, I have put my new keystore in my git repo. Fall
back
Regards,
On Mon, Jun 18, 2012 at 6:41 AM, Saurav to.saurav.mukher...@gmail.com wrote:
Anyways, as you all said, I have put my new keystore in my git repo.
Um, I really hope that's a private repo. Backed up does not mean
published for the world to see.
--
Mark Murphy (a Commons Guy)
Ha ha!
It is not public, Mark.
Regards,
Saurav Mukherjee.
On Mon, Jun 18, 2012 at 4:14 PM, Mark Murphy mmur...@commonsware.comwrote:
see
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
On Mon, Jun 18, 2012 at 7:31 AM, Saurav to.saurav.mukher...@gmail.com wrote:
Ha ha!
It is not public, Mark.
That's good. I'm willing to bet that there's a few dozen projects
floating around, though, who *did* upload their keystore into a public
git repo. That's bad -- they are one Google
I understand!
Thanks again everyone!
Regards,
Saurav Mukherjee.
On Mon, Jun 18, 2012 at 8:32 PM, Mark Murphy mmur...@commonsware.comwrote:
On Mon, Jun 18, 2012 at 7:31 AM, Saurav to.saurav.mukher...@gmail.com
wrote:
Ha ha!
It is not public, Mark.
That's good. I'm willing to bet that
Thanks Mark.
You have always helped me out, now and in the past!
I know that the encryption is irreversible, wanted to know if there is a
workaround for upgrading!
Could someone convey this to Google, that, loosing a keystore is possible,
highly STUPID, but possible.
They should have a fall back
On Thu, Jun 14, 2012 at 10:35 AM, Saurav to.saurav.mukher...@gmail.com wrote:
Thanks Mark.
You have always helped me out, now and in the past!
I know that the encryption is irreversible, wanted to know if there is a
workaround for upgrading!
Could someone convey this to Google, that, loosing
On Thu, Jun 14, 2012 at 10:35 AM, Saurav to.saurav.mukher...@gmail.com wrote:
They should have a fall back plan! To upgrade the application, with another
keystore or some other secure procedure. Just a thought!
That would be the responsibility of the Play Store people, who are not
on this list
On Thu, Jun 14, 2012 at 9:05 AM, Mark Murphy mmur...@commonsware.comwrote:
On Thu, Jun 14, 2012 at 10:35 AM, Saurav to.saurav.mukher...@gmail.com
wrote:
They should have a fall back plan! To upgrade the application, with
another
keystore or some other secure procedure. Just a thought!
On Thu, Jun 14, 2012 at 9:35 AM, Saurav to.saurav.mukher...@gmail.comwrote:
Could someone convey this to Google, that, loosing a keystore is possible,
highly STUPID, but possible.
They should have a fall back plan!
Really though, *you* should have a fall back plan. You backed up your APKs?
Hi all,
I am in a bit of a soup.
I have lost my keystore file for my signed apk, which is in market. Is
there any way I can extract the certificate from the backup apks that I
have?
Any hack? Please. Mercy. I really need to push an update to the application
in the market.
Thanks in advance!
On Wed, Jun 13, 2012 at 12:00 PM, Saurav to.saurav.mukher...@gmail.com wrote:
I have lost my keystore file for my signed apk, which is in market. Is there
any way I can extract the certificate from the backup apks that I have?
No. It is mathematically impossible to recover a keystore from
No. It is mathematically impossible to recover a keystore from
something signed with that keystore.
I know this isn't related to the list, but I've always wondered about that
part. Could anybody explain how it is mathematically impossible, or point
me to a good link?
Thanks
--
Raghav Sood
On Wed, Jun 13, 2012 at 12:53 PM, Raghav Sood raghavs...@gmail.com wrote:
I know this isn't related to the list, but I've always wondered about that
part. Could anybody explain how it is mathematically impossible
Digital signatures are based upon public-key cryptography. You cannot
recover a
That's right, this should be covered in any basic crypto text..
kris
On Wed, Jun 13, 2012 at 12:53 PM, Raghav Sood raghavs...@gmail.com wrote:
No. It is mathematically impossible to recover a keystore from
something signed with that keystore.
I know this isn't related to the list, but I've
Digital signatures are based upon public-key cryptography. You cannot
recover a private key given a public key -- that's the whole point of
public-key crypto. Such algorithms are based on one-way functions:
things that are easy to do but hard to reverse.
This is enough. I know what public
21 matches
Mail list logo
