![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| SuSE SUSE Linux is a major operating system. The developer rights are owned by Novell, Inc. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| ssh-keygen questions (not working) | tekline | UNIX for Advanced & Expert Users | 10 | 09-01-2008 09:17 PM |
| Dare We Outsource Trust? | iBot | IT Security RSS | 0 | 05-30-2008 09:40 AM |
| Wikipedia: Trust but Verify | iBot | IT Security RSS | 0 | 05-28-2008 03:50 PM |
| How to shutdown Power Trust UPS Monitoring? | kanpatel | HP-UX | 3 | 11-06-2007 11:56 AM |
| problem with dd command or maybe AFS problem | Anta | Shell Programming and Scripting | 0 | 08-25-2006 10:10 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
ssh-keygen trust problem
OK, this is the problem. I have 2 machines TestA ( Suse 9.0 ) TestB ( Mandrake 10 ) and one of our guys wants to scp from TestA to TestB without the password prompt appearing. Sounds simple so far....
Ok, I haven't used ssh-keygen before, so I create identical logins to test what I'm doing... TestA ~user/.ssh > ssh-keygen -t dsa -f ./id_dsa ( Hit enter to set blank password ) TestA ~user/.ssh > scp id_dsa.pub user@TestA:~/.ssh ( use password ) TestB ~user/.ssh > cd ~user/.ssh TestB ~user/.ssh > mv id_dsa.pub authorized_keys2 TestB ~user/.ssh > rm id_dsa.pub It now works fine for the test logins, but when I try to apply this to the guy upstairs logins it still asks for the passwords.... I assume it must be down to some kind of difference in the logins but I can't really find any... Any ideas ???? |
|
||||
|
I shall humbly hold my head in shame.....
The problem was caused by the ~user/.ssh directory having 755 permissions instead off 700 on one of the boxes.... Obviously ssh protocol doesn't like the idea of having it's key files open for anyone other than the user.... Cheers for the help guys... |
| Sponsored Links | ||
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|