SSH keygen and login problem

Paul Preston Paul.Preston at proxar.co.uk
Wed Jan 12 14:52:55 UTC 2011


Hi,

633 for authorised_keys - interesting...

Please change it to 700, copy  the content of authorised_keys manually and try "ssh -v <host>"

This should show you why you can't use ssh key to authenticate.

Kind regards,

--
Paul Preston
Proxar IT Ltd. Registered in England and Wales: 6744401- VAT: 942985479
Tubs Hill House, London Road, Sevenoaks, Kent, TN13 1BL
Tel:  (+44) 0844 809 4335
Fax: (+44) 01732 459 423
Mob: (+44) 077 9509 3450
Web: www.proxar.co.uk
Email: paul.preston at proxar.co.uk


-----Original Message-----
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com] On Behalf Of a bv
Sent: 12 January 2011 14:07
To: General Red Hat Linux discussion list
Subject: Re: SSH keygen and login problem

hi

the .ssh is  drwx------

i changed from 600 to 633 for authorized_keys  but still asking for password

i checked  before ssh-copy-id doesnt seem to be exit on Checkpoint SPLAT . i login with my normal user then use the expert command (which is like su) i use the root privilegs for key creating)

2011/1/12, Abhilash abhi <abhilashck72 at gmail.com>:
> Hi,
>
> Why cant u use "ssh-copy-id -i ~/.ssh/id_dsa.pub
> user at IPaddress"(Destination)..
> It will automatically copy the public key to ur destination. And u are
> creating the key as root or normal user ?
>
> Thanks,
>
>
>
> On Wed, Jan 12, 2011 at 5:43 PM, Johan Booysen
> <johan at matrixsolutions.co.uk>wrote:
>
>> Might be worth checking the permissions on the .ssh directory and on
>> the authorized_keys file.  That's bitten me before, and should be:
>>
>> drwx------      .ssh
>> -rw-r--r--      authorized_keys
>>
>> -----Original Message-----
>> From: redhat-list-bounces at redhat.com
>> [mailto:redhat-list-bounces at redhat.com] On Behalf Of a bv
>> Sent: 12 January 2011 11:27
>> To: redhat-list at redhat.com
>> Subject: SSH keygen and login problem
>>
>>  Hi,,
>>
>> For my file transfer script i want to use scp without password. Here
>> is nearly what i have done:
>> 1- I logined to my Checkpoint (which is Redhat based and the one who
>> is source) with my personal user and gave expert command  to have
>> root permissons.
>> 2. Changed directory to /root/.ssh and gave ssh-keygen -t dsa and
>> created the key pairs.
>> 3 I copied yhe public key to my home folder at the remote server
>> like
>>
>> scp ~/.ssh/id_dsa.pub
>> myuser at remoteserver:/home/myuser.ssh/authorized_keys
>>
>> 4. Then i copied this authorized_keys to the /root/.ssh.
>> 5 then tried to send a sample file from my Checkpoint box to remote
>> server with scp but it requested me to enter a password.
>>
>> how can i fix this ? then ill adapt my scirpt to this regards.
>>
>> --
>> redhat-list mailing list
>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/redhat-list
>>
>> --
>> redhat-list mailing list
>> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/redhat-list
>>
>
>
>
> --
>
> Regards,
> Abhilash
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>

--
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
Please note that we may monitor or record telephone calls, email traffic data and also the content of email for the purposes of security and staff training. This message (and any associated files or documentation) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files and documentation associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.




More information about the redhat-list mailing list