I mean to say Note: no -keypass parameter. It is not legal Not
-storepass. Sorry if I added to anyone's confusion!
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To
21.03.2011 13:36, Bob Kerns пишет:
I mean to say Note: no -keypass parameter. It is not legal Not
-storepass. Sorry if I added to anyone's confusion!
It makes sense that getting a list of keys requires the keystore
password, not passwords for individual keys.
However, this only highlights
On Mon, Mar 21, 2011 at 4:48 PM, Kostya Vasilyev kmans...@gmail.com wrote:
Android docs say this:
http://developer.android.com/guide/publishing/app-signing.html#setup
If you are developing on a version of Linux that originally came with GNU
Compiler for Java, make sure that the system is
There is also the ever-useful which command, as in:
which keytool
will tell you which keytool (!) is getting executed when you type keytool.
I don't remember if which follows links, so just in case, the
following should show link target, if the keytool on the path is
actually a link:
ls
Actually, just to pedantically clear up one potential source of confusion --
you're not getting a list of keys, you're getting a list of aliases for
entries, which can be one of three things:
1) A trusted certificate entry (what trusted means here depends on how the
keystore is being used) --
Sigh. Everybody here is confused, including Mark and the documentation.
The -list argument to keytool *does not take the -keypass argument.*
*
*
It makes absolutely no sense whatsoever for it to take it. It does not
provide you with any information about the private key, and thus has no need
As a side comment: I am not the slightest bit surprised that everyone is
confused.
I don't know why cryptography tools and APIs and documentation have to be so
incredibly cryptic.
Clearly the fact that *everyone *is confused should suggest that the problem
does not lie with the confused
now,
what do you suggest i should do... please help me out here i
have been struggling with this thing for the past 2 days
stackOverflow isn't coming out to be helpful either. PLEASE PLEASE PLEASE
help me out on this.
here is the discussion on the same topic at
stackoverflow.comhttp://goo.gl/b7slO
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send
On Sat, Mar 19, 2011 at 9:03 AM, Syed Rakib Al Hasan
syed.rakib.al.ha...@gmail.com wrote:
here is the discussion on the same topic at stackoverflow.com
And your answer is now on the same topic at stackoverflow.com:
Your keytool appears to be from the GNU Compiler for Java. Android
requires the
On Saturday, March 19, 2011 7:08:26 PM UTC+6, Mark Murphy (a Commons Guy)
wrote:
Try using the keytool from a supported Java environment.
how do i do that
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group,
On Sat, Mar 19, 2011 at 9:20 AM, Syed Rakib Al Hasan
syed.rakib.al.ha...@gmail.com wrote:
On Saturday, March 19, 2011 7:08:26 PM UTC+6, Mark Murphy (a Commons Guy)
wrote:
Try using the keytool from a supported Java environment.
how do i do that
I'd start by installing a supported Java
On Saturday, March 19, 2011 7:08:26 PM UTC+6, Mark Murphy (a Commons Guy)
wrote:
Try using the keytool from a supported Java environment.
how do i do that can you please help me with providing some steps on how
to get such a keytool?
--
You received this message because you are
On Sat, Mar 19, 2011 at 7:24 PM, Mark Murphy mmur...@commonsware.comwrote:
I'd start by installing a supported Java environment.
well, I believe i do have that what exactly do you mean by a *
SUPPORTED* java environment? I have the Sun-Java-6 installed in my Linux
Ubuntu. how do i use
On Sat, Mar 19, 2011 at 9:29 AM, Syed Rakib Al Hasan
syed.rakib.al.ha...@gmail.com wrote:
On Sat, Mar 19, 2011 at 7:24 PM, Mark Murphy mmur...@commonsware.com
wrote:
I'd start by installing a supported Java environment.
well, I believe i do have that what exactly do you mean by a
thanks man.. i have found my solution by using the keytool from the
Java6 bin directory. and it has worked in a snap.
however, to understand this thing better.. seeing from the link you
suggested i have tried the following in my terminal and this is what i found
That may be a bug in the Ubuntu update-java-alternatives, then. It
should fix up all those references.
I use Ubuntu, but I do not have GCJ installed, so I get the right
keytool by default.
You can either:
-- remove GCJ, if you are not otherwise using it, and
update-java-alternatives again
--
@MarkMurphy - thank you so very much.. things are making much more sense
now.
so... in case anyone is having any SIMILAR kind of problem with the
keytool.. here is what i wrote down summarizing all the findings and
help from you guys.
i used linux ubuntu 10.10... my *debug.keystore* file is in the location
~/.android/debug.keystore.
i used the following terminal commands as explained in
http://code.google.com/android/add-ons/google-apis/mapkey.html
keytool -list -alias androiddebugkey -keystore
Sounds like you are getting some weird (obsolete?) version of keytool,
due to having multiple installed versions.
18.03.2011 23:16, Syed Rakib Al Hasan ?:
i used linux ubuntu 10.10... my */debug.keystore/* file is in the
location|~/.android/debug.keystore|.
i used the following
20 matches
Mail list logo