Gordon Messmer writes:
> On Sun, 18 Nov 2001, Ian Truelsen wrote:
>
>> Andreas Hansson writes:
>> > Try checking the permissions of the files and directories. ssh doesn't like
>> > if ~/.ssh/identity is readable by anyone but owner. Also authorized_keys
>> > shouldn't be writeable by anyone b
On Sun, 18 Nov 2001, Ian Truelsen wrote:
> Andreas Hansson writes:
> > Try checking the permissions of the files and directories. ssh doesn't like
> > if ~/.ssh/identity is readable by anyone but owner. Also authorized_keys
> > shouldn't be writeable by anyone but owner.
> >
> The permissions
Bret Hughes writes:
> Ian Truelsen wrote:
>
>> Dave Reed writes:
>>
>> > Looks to me like it's trying protocol 1 and then protocol 2. Which are
>> > you trying to use? I've got it working using protocol 2.
>> >
>> > For protocol 2, you should have an id_dsa and an id_dsa.pub on the
>> > local
Dave Reed writes:
>> From: "Ian Truelsen" <[EMAIL PROTECTED]>
>>
>> Dave Reed writes:
>>
>>
>> > Looks to me like it's trying protocol 1 and then protocol 2. Which are
>> > you trying to use? I've got it working using protocol 2.
>> >
>> > For protocol 2, you should have an id_dsa and an
Ian Truelsen wrote:
> Dave Reed writes:
>
> > Looks to me like it's trying protocol 1 and then protocol 2. Which are
> > you trying to use? I've got it working using protocol 2.
> >
> > For protocol 2, you should have an id_dsa and an id_dsa.pub on the
> > local machine. The remote machine should
> From: "Ian Truelsen" <[EMAIL PROTECTED]>
>
> Dave Reed writes:
>
>
> > Looks to me like it's trying protocol 1 and then protocol 2. Which are
> > you trying to use? I've got it working using protocol 2.
> >
> > For protocol 2, you should have an id_dsa and an id_dsa.pub on the
> > local ma
I found these two articles *very* helpful in setting up ssh passwordless
login:
http://www-106.ibm.com/developerworks/library/l-keyc.html
and
http://www-106.ibm.com/developerworks/library/l-keyc2/
The second mainly deals with keychain, a handy little program that starts up
at login and it i
Dave Reed writes:
> Looks to me like it's trying protocol 1 and then protocol 2. Which are
> you trying to use? I've got it working using protocol 2.
>
> For protocol 2, you should have an id_dsa and an id_dsa.pub on the
> local machine. The remote machine should have its own id_dsa and
> id_
On Sun, Nov 18, 2001 at 05:58:38PM +, Ian Truelsen wrote:
>
> The permissions are fine.
>From the machine you're trying to connect from, type:
ssh -v hostname
where hostname is the name of the machine you're trying to connect to.
Emmanuel
___
> >
> > I haven't read all the messages in this thread carefully, but have you
> > sent the output of ssh -v to the list? That should tell us where the
> > problem is (i.e., ssh -v hostname, where hostname is the name of the
> > machine you are connecting to).
> >
> Here is the output of ssh -v
Dave Reed writes:
>> From: "Ian Truelsen" <[EMAIL PROTECTED]>
>>
>> Cameron Simpson writes:
>>
>> > On Sun, Nov 18, 2001 at 12:53:24AM +, Ian Truelsen <[EMAIL PROTECTED]>
>wrote:
>> > | > Say this:
>> > | >eval `ssh-agent`
>> > | > That will start one and also tell your shell
> From: "Ian Truelsen" <[EMAIL PROTECTED]>
>
> Cameron Simpson writes:
>
> > On Sun, Nov 18, 2001 at 12:53:24AM +, Ian Truelsen <[EMAIL PROTECTED]>
>wrote:
> > | > Say this:
> > | > eval `ssh-agent`
> > | > That will start one and also tell your shell enough for the other command
Cameron Simpson writes:
> On Sun, Nov 18, 2001 at 12:53:24AM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
> | > Say this:
> | > eval `ssh-agent`
> | > That will start one and also tell your shell enough for the other commands
> | > to contact it.
> |
> | Tried the eval 'ssh-agent' and I st
On Sun, Nov 18, 2001 at 12:53:24AM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
| > Say this:
| > eval `ssh-agent`
| > That will start one and also tell your shell enough for the other commands
| > to contact it.
|
| Tried the eval 'ssh-agent' and I still get the same error when I run
| s
Andreas Hansson writes:
>> Anyway, all that corrected and it still gives me exactly the same error,
> or
>> warning as you will. Either way, it doesn't work.
>>
>> If you can think of anything else that I might have missed, I'd appreciate
>> it.
>
> Try checking the permissions of the files an
> Anyway, all that corrected and it still gives me exactly the same error,
or
> warning as you will. Either way, it doesn't work.
>
> If you can think of anything else that I might have missed, I'd appreciate
> it.
Try checking the permissions of the files and directories. ssh doesn't like
if ~/.
Werner Puschitz writes:
>
> On Sat, 17 Nov 2001, David Talkington wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Ian Truelsen wrote:
>>
>>
>> >Now, when you said to put the authourized_keys at the far end, did you mean
>> >in HOME$/.ssh/authourized_keys or somewhere
On Sat, 17 Nov 2001, David Talkington wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Ian Truelsen wrote:
>
>
> >Now, when you said to put the authourized_keys at the far end, did you mean
> >in HOME$/.ssh/authourized_keys or somewhere else?
>
> Check your spelling. You want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ian Truelsen wrote:
>Now, when you said to put the authourized_keys at the far end, did you mean
>in HOME$/.ssh/authourized_keys or somewhere else?
Check your spelling. You want the western incantation of
"authorized_keys".
- -d
- --
David
Cameron Simpson writes:
> On Sun, Nov 18, 2001 at 12:11:51AM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
> | > Make yourself a key pair with the shh-keygen command and copy the
> | > public half into the .ssh/authorized_keys at the far end.
> | > Then make sure you have an ssh-agent, and pla
Cameron Simpson writes:
> On Sun, Nov 18, 2001 at 12:11:51AM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
> | > Make yourself a key pair with the shh-keygen command and copy the
> | > public half into the .ssh/authorized_keys at the far end.
> | > Then make sure you have an ssh-agent, and pla
On Sun, Nov 18, 2001 at 12:11:51AM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
| > Make yourself a key pair with the shh-keygen command and copy the
| > public half into the .ssh/authorized_keys at the far end.
| > Then make sure you have an ssh-agent, and place your key into it with ssh-add.
Cameron Simpson writes:
> On Sat, Nov 17, 2001 at 11:24:36PM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
> | I have been trying to set up a command-line call to a program on another
> | machine using SSH. It works fine when I call it from a term and enter the
> | password, but I am trying t
On Sat, Nov 17, 2001 at 11:24:36PM +, Ian Truelsen <[EMAIL PROTECTED]> wrote:
| I have been trying to set up a command-line call to a program on another
| machine using SSH. It works fine when I call it from a term and enter the
| password, but I am trying to set it up so that I don't have t
I have been trying to set up a command-line call to a program on another
machine using SSH. It works fine when I call it from a term and enter the
password, but I am trying to set it up so that I don't have to do this.
From the man pages, I was able to figure out that I should be able to get
25 matches
Mail list logo
