At 07:56 AM 1/19/2004, Marc Poppleton you wrote:
>> There is not a lot else the Cygwin list can help with as it appears from
>> the verbose output you previously posted that the Cygwin ssh client is
>> doing exactly what it should and the problem lies with the Linux sshd
>> server.
>
>That all I ac
> There is not a lot else the Cygwin list can help with as it appears from
> the verbose output you previously posted that the Cygwin ssh client is
> doing exactly what it should and the problem lies with the Linux sshd
> server.
That all I actually needed to know! :)
I was affraid that something
Marc Poppleton wrote:
> > So, none of us are mindreaders here, and we have zero information about
> > the configuration details of your sshd, which isn't even running
> > Cygwin... So, don't don't be surprised if you are underwhelmed with
> > help.
>
> Well, concerning running Cygwin, I get the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 19 Jan 2004 12:06:54 +0100, Marc Poppleton <[EMAIL PROTECTED]> wrote:
>
> > The problem's probably on the server end. It must be configured to
> > accept pubkey auth, as well as having your public key installed
> > properly. You can see that t
AIL PROTECTED]>
cc: (bcc: Jurgen Defurne/BRG/CE/PHILIPS)
Subject:RE: SSH key authentification problem
Classification:
> The problem's probably on the server end. It must be configured to
> accept pubkey auth, as well as having your public key ins
On 19 January 2004 12:06 +0100 Marc Poppleton wrote:
> The problem's probably on the server end. It must be configured to
> accept pubkey auth, as well as having your public key installed
> properly. You can see that the client tries pubkey but it's not
> accepted.
Yes, this is what it looks like
> The problem's probably on the server end. It must be configured to
> accept pubkey auth, as well as having your public key installed
> properly. You can see that the client tries pubkey but it's not
> accepted.
Yes, this is what it looks like to me.
> So, none of us are mindreaders here, and w
Marc Poppleton wrote:
> debug1: Authentications that can continue: publickey,password
> debug1: Next authentication method: publickey
> debug1: Trying private key: /cygdrive/c/.ssh/identity
> debug1: Trying private key: /cygdrive/c/.ssh/id_rsa
> debug1: Offering public key: /cygdrive/c/.ssh/id_dsa
sword after?
Marc
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part
> de [EMAIL PROTECTED]
> Envoye : lundi 19 janvier 2004 11:05
> Cc : [EMAIL PROTECTED]
> Objet : RE: SSH key authentification problem
>
>
> Marc,
>
> My sug
Defurne/BRG/CE/PHILIPS)
Subject:RE: SSH key authentification problem
Classification:
Jurgen and Olaf,
I have done as you suggested:
chmod 700 .ssh
chmod 600 .ssh/*
Nothing different when I try my ssh -i id_dsa [EMAIL PROTECTED] I've
tried
gi
Jurgen and Olaf,
I have done as you suggested:
chmod 700 .ssh
chmod 600 .ssh/*
Nothing different when I try my ssh -i id_dsa [EMAIL PROTECTED] I've tried
giving a wrong filename and I got an answer saying this file didn't exist
(which is normal).
Here is what I get when I do ssh
On Mon, Jan 19, 2004 at 10:44:25AM +0100, [EMAIL PROTECTED] wrote:
> Marc,
>
> I had Saturday the same problem in the course I am
> giving. After a few minutes, it started to dawn : check
> your access rights :
> $HOME/.ssh should be rwx-- (700)
> $HOME/.ssh/* should be rw--- (600)
And yo
Marc,
I had Saturday the same problem in the course I am
giving. After a few minutes, it started to dawn : check
your access rights :
$HOME/.ssh should be rwx-- (700)
$HOME/.ssh/* should be rw--- (600)
Jurgen
"Marc Poppleton" <[EMAIL PROTECTED]>
Sent by:
[EMAIL PROTECTED]
01/19
13 matches
Mail list logo
