Hi Team,
I don't want to get mails from this community any more. Please unsubscribe
me from this list.
Thanks you very much.
Regards,
Guru Prasad
From:
Gerry Reno <***@verizon.net>
To:
jsch-***@lists.sourceforge.net
Date:
11/11/2013 08:53 PM
Subject:
Re: [JSch-users] addIdentity: on android getting invalid privatekey:
[***@428ff138 with known good RSA key
Hi Volker,
Thanks for the reply.
I should have mentioned that I already had both public and private
keys in the same folder on the Android device.
The keys have the same prefix only difference is that .pub is added for
public key. Eg: id_rsa and id_rsa.pub.
I had read about needing the public key in the folder when I checked
the method.
The perms on both files are rw-rw-r-- when I upload the keys. And
without a rooted phone I have no way to change
those permissions. Could this be a factor?
If so, I guess I could read the file into a String and call one of the
alternate methods although I'd really prefer
to just use the simpler method. Any way to get that working?
Post by Jung, VolkerHello Gerry,
when using the addIdentity-Method taking only the private-key-path, the
public key is expected to be in the same folder as the private key, having
the same name as the private key with an additional suffix ".pub". (See
KeyPair.load(JSch, String, String)). You might want to use one of the
other addIdentity-Methods provided by the JSch-class to be independent of
that default behavior.
Post by Jung, Volker-----Ursprüngliche Nachricht-----
Gesendet: Sonntag, 10. November 2013 21:31
Betreff: [JSch-users] addIdentity: on android getting invalid
Using JSch 1.50
I'm trying to get publickey auth working on arm android.
I have password auth working fine already.
So I added addIdentity( keypath ) but it always errors even with known good RSA key.
I tested the key both on the phone using ConnectBot and on two linux machines using openssh.
The key works fine from all three.
When I use the addIdentity method and pass the key path I'm always
Is there something else I need to add besides addIdentity to make this work?
------------------------------------------------------------------------------
Post by Jung, VolkerNovember Webinars for C, C++, Fortran Developers Accelerate application
performance with scalable programming models. Explore techniques for
threading, error checking, porting, and tuning. Get the most from the
latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
Post by Jung, Volker_______________________________________________
JSch-users mailing list
https://lists.sourceforge.net/lists/listinfo/jsch-users
------------------------------------------------------------------------------
Post by Jung, VolkerNovember Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models.
Explore
Post by Jung, Volkertechniques for threading, error checking, porting, and tuning. Get the
most
Post by Jung, Volkerfrom the latest Intel processors and coprocessors. See abstracts and
register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
Post by Jung, Volker_______________________________________________
JSch-users mailing list
https://lists.sourceforge.net/lists/listinfo/jsch-users
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models.
Explore
techniques for threading, error checking, porting, and tuning. Get the
most
from the latest Intel processors and coprocessors. See abstracts and
register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
JSch-users mailing list
JSch-***@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jsch-users
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you