|
|
 Up |
|
|
  |
Author: RonaldOttoValentinFischerRonaldOttoValentinFischer Date: May 8, 2008 07:16
Could somebody help me here? While I use Putty to access a
remote host via ssh, it doesn't work with Cygwin's ssh. Here
is what I have:
# This is my private key file
$ ls -l /cygdrive/h/etcsec/fischron.ppk
-rw------- 1 fischron mkgroup-l-d 802 May 8 16:06 /cygdrive/h/etcsec/
fischron.ppk
$ ls -dl etcsec
drwx------+ 1 fischron mkgroup-l-d 0 May 8 16:06 etcsec
|
| Show full article (0.98Kb) |
|
| | 9 Comments |
|
|
Author: RonaldOttoValentinFischerRonaldOttoValentinFischer Date: May 8, 2008 07:29
Additional information to my posting:
I found that this error message was only caused when the environment
variable CYGWIN was
not set to smbntsec.
When I do an
export CYGWIN=smbntsec
ssh now asks me
Enter passphrase for key 'etcsec/fischron.ppk':
which is also strange, since the whole purpose of passing the private
key file to ssh ist that
I don't have to specify a passphrase. What else am I missing?
Ronald
|
| |
|
| | no comments |
|
|
Author: Chris MatternChris Mattern Date: May 8, 2008 07:48
On 2008-05-08, RonaldOttoValentinFischer gmail.com> wrote:> Could somebody help me here? While I use Putty to access a
> remote host via ssh, it doesn't work with Cygwin's ssh. Here
> is what I have:
>
> # This is my private key file
> $ ls -l /cygdrive/h/etcsec/fischron.ppk
> -rw------- 1 fischron mkgroup-l-d 802 May 8 16:06 /cygdrive/h/etcsec/
> fischron.ppk
>
> $ ls -dl etcsec
> drwx------+ 1 fischron mkgroup-l-d 0 May 8 16:06 etcsec
>
> # This is what ssh says:
> mucn13154:~ 1 199 $ ssh -i $HOME/etcsec/fischron.ppk -2 -p 22
> fischron@...
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> @ WARNING: UNPROTECTED PRIVATE KEY FILE! @
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> Permissions 0644 for '/cygdrive/h/etcsec/fischron.ppk' are too open. ...
|
| Show full article (1.35Kb) |
| no comments |
|
|
Author: Simon TathamSimon Tatham Date: May 8, 2008 08:14
RonaldOttoValentinFischer gmail.com> wrote:> ssh now asks me
>
> Enter passphrase for key 'etcsec/fischron.ppk':
>
> which is also strange, since the whole purpose of passing the
> private key file to ssh is that I don't have to specify a
> passphrase. What else am I missing?
Are you sure your key is in the right format? I haven't heard that
OpenSSH can handle PuTTY's .ppk format for private keys. (Of course,
if it can and nobody's happened to tell me, that'd be great!)
--
Simon Tatham "Thieves respect property; they only wish the property to
pobox.com> be their own, that they may more properly respect it."
|
| |
| no comments |
|
|
Author: Nico Kadel-GarciaNico Kadel-Garcia Date: May 8, 2008 13:01
On 8 May, 16:14, Simon Tatham pobox.com> wrote:> RonaldOttoValentinFischer  gmail.com> wrote:>> ssh now asks me
>
>> Â Enter passphrase for key 'etcsec/fischron.ppk':
>
>> which is also strange, since the whole purpose of passing the
>> private key file to ssh is that I don't have to specify a
>> passphrase. What else am I missing?
>
> Are you sure your key is in the right format? I haven't heard that
> OpenSSH can handle PuTTY's .ppk format for private keys. (Of course,
> if it can and nobody's happened to tell me, that'd be great!)
> --
> Simon Tatham     "Thieves respect property; they only wish the property to
> pobox.com> Â Â be their own, that they may more properly respect it."
It still can't. You need to use Puttygen to transform it properly to
the OpenSSH compatible format.
|
| Show full article (1.01Kb) |
| no comments |
|
|
Author: RonaldOttoValentinFischerRonaldOttoValentinFischer Date: May 9, 2008 01:39
On 8 Mai, 16:48, Chris Mattern sumire.gwu.edu> wrote:> On 2008-05-08, RonaldOttoValentinFischer gmail.com> wrote:
>
>
>>> Could somebody help me here? While I use Putty to access a
>> remote host via ssh, it doesn't work with Cygwin's ssh. Here
>> is what I have:
>
>> # This is my private key file
>> $ ls -l /cygdrive/h/etcsec/fischron.ppk
>> -rw------- 1 fischron mkgroup-l-d 802 May 8 16:06 /cygdrive/h/etcsec/
>> fischron.ppk
>
>> $ ls -dl etcsec
>> drwx------+ 1 fischron mkgroup-l-d 0 May 8 16:06 etcsec
>
>> # This is what ssh says:
>> mucn13154:~ 1 199 $ ssh -i $HOME/etcsec/fischron.ppk -2 -p 22
>> fischron@... ...
|
| Show full article (1.46Kb) |
| no comments |
|
|
Author: RonaldOttoValentinFischerRonaldOttoValentinFischer Date: May 9, 2008 01:42
On 8 Mai, 17:14, Simon Tatham pobox.com> wrote:> Are you sure your key is in the right format? I haven't heard that
> OpenSSH can handle PuTTY's .ppk format for private keys. (Of course,
> if it can and nobody's happened to tell me, that'd be great!)
If this is so, it could be indeed the reason!! Actually, I thought
everything dealing
with ssh is standardized, so I assumed that I can use the same key
file for putty and for Cygwin's ssh.
So how would I have to proceed, if I want to use putty and Cygwin ssh
on the same machine in order to connect to a remote host?
Ronald
|
| |
| no comments |
|
|
Author: Simon TathamSimon Tatham Date: May 9, 2008 02:31
RonaldOttoValentinFischer gmail.com> wrote:> If this is so, it could be indeed the reason!! Actually, I thought
> everything dealing with ssh is standardized, so I assumed that I can
> use the same key file for putty and for Cygwin's ssh.
Unfortunately not: I know of three different formats for SSH-2
private key files. (The SSH-1 private key format _is_ de-facto
standardised, oddly.)
This is at least partly my fault: I invented a new format for
PuTTY's private keys instead of using one of the existing formats.
There was a reason, however: PuTTY's key format keeps the public key
in...
|
| Show full article (1.71Kb) |
| no comments |
|
|
Author: Simon TathamSimon Tatham Date: May 9, 2008 02:33
Nico Kadel-Garcia gmail.com> wrote:> And Hi, Simon! Thanks for your work with Putty: any word on when it
> might incorporate GSSAPI directly, rather than requiring me to get the
> fork from Quest Software?
As it happens, Owen is actively working on integrating GSSAPI into
the main PuTTY source base. I can't promise exactly when that might
happen, but I'd certainly expect it by the next release. (he says,
having no real idea when _that_ might happen either :-)
--
Simon Tatham "infinite loop _see_ loop, infinite"
pobox.com> - Index, Borland Pascal Language Guide
|
| |
| no comments |
|
|
|
|
|
Author: Nico Kadel-GarciaNico Kadel-Garcia Date: May 9, 2008 16:05
Simon Tatham wrote:
> Nico Kadel-Garcia gmail.com> wrote:>> And Hi, Simon! Thanks for your work with Putty: any word on when it
>> might incorporate GSSAPI directly, rather than requiring me to get the
>> fork from Quest Software?
>
> As it happens, Owen is actively working on integrating GSSAPI into
> the main PuTTY source base. I can't promise exactly when that might
> happen, but I'd certainly expect it by the next release. (he says,
> having no real idea when _that_ might happen either :-)
Good. The other package is useful, but the installer is not so good as yours,
and I'd rather see such features in the main codeline.
|
| |
| no comments |
|
|
