<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic SSH keygen auth problems in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341964#M72645</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a situation where I would like to use secure keys to send data between to Suse SLES 8 hosts, but I am having difficulty in creating successful keys.&lt;BR /&gt;&lt;BR /&gt;Currently I am trying ssh-keygen -d on both hostA and hostB then copying the id_dsa.pub to authorized_keys on the 'other' hosts.&lt;BR /&gt;&lt;BR /&gt;after this I am using ssh-agent sh -c'ssh-add' which tells me that the identity has been successfully added.&lt;BR /&gt;&lt;BR /&gt;The problem that I have is that the process although I have used the same procedure on both boxes is only working on one of them. I.E:I can ssh HostA from HostB without having to type in a password. When I try to use it the other way around, the ssh process keeps asking me to type in the password for user@HostB. I hope my info is not too vague. &lt;BR /&gt;&lt;BR /&gt;Any help would be greatly appreciated.I wonder if I have missed something or if there is a default file that may exist on the unsuccessful machine.&lt;BR /&gt;&lt;BR /&gt;Many thanks</description>
    <pubDate>Tue, 27 Jul 2004 06:48:25 GMT</pubDate>
    <dc:creator>Matt Palmer_2</dc:creator>
    <dc:date>2004-07-27T06:48:25Z</dc:date>
    <item>
      <title>SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341964#M72645</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I have a situation where I would like to use secure keys to send data between to Suse SLES 8 hosts, but I am having difficulty in creating successful keys.&lt;BR /&gt;&lt;BR /&gt;Currently I am trying ssh-keygen -d on both hostA and hostB then copying the id_dsa.pub to authorized_keys on the 'other' hosts.&lt;BR /&gt;&lt;BR /&gt;after this I am using ssh-agent sh -c'ssh-add' which tells me that the identity has been successfully added.&lt;BR /&gt;&lt;BR /&gt;The problem that I have is that the process although I have used the same procedure on both boxes is only working on one of them. I.E:I can ssh HostA from HostB without having to type in a password. When I try to use it the other way around, the ssh process keeps asking me to type in the password for user@HostB. I hope my info is not too vague. &lt;BR /&gt;&lt;BR /&gt;Any help would be greatly appreciated.I wonder if I have missed something or if there is a default file that may exist on the unsuccessful machine.&lt;BR /&gt;&lt;BR /&gt;Many thanks</description>
      <pubDate>Tue, 27 Jul 2004 06:48:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341964#M72645</guid>
      <dc:creator>Matt Palmer_2</dc:creator>
      <dc:date>2004-07-27T06:48:25Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341965#M72646</link>
      <description>ssh-keygen -d&lt;BR /&gt;creates by default the file ~/.ssh/id_dsa.pub&lt;BR /&gt;&lt;BR /&gt;you have to copy it to destined machine:&lt;BR /&gt;x.x.x.x:/home/username/.ssh/authorized_keys&lt;BR /&gt;then when issuing this command:&lt;BR /&gt;ssh username@x.x.x.x&lt;BR /&gt;you'll login to this machine without the prompt of username password.Check that you do exactly the same steps...</description>
      <pubDate>Tue, 27 Jul 2004 06:59:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341965#M72646</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2004-07-27T06:59:00Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341966#M72647</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;this is what I have tried already, but it is not working on the 2nd machine.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;&lt;BR /&gt;Matt&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Jul 2004 07:01:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341966#M72647</guid>
      <dc:creator>Matt Palmer_2</dc:creator>
      <dc:date>2004-07-27T07:01:50Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341967#M72648</link>
      <description>Remove the files authorized_keys ,known_hosts&lt;BR /&gt;from the "bad" machine and try the procedure again.&lt;BR /&gt;In case it doesn't help try reinstalling&lt;BR /&gt;the openssh package.</description>
      <pubDate>Tue, 27 Jul 2004 07:27:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341967#M72648</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2004-07-27T07:27:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341968#M72649</link>
      <description>still no joy..</description>
      <pubDate>Tue, 27 Jul 2004 09:18:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341968#M72649</guid>
      <dc:creator>Matt Palmer_2</dc:creator>
      <dc:date>2004-07-27T09:18:20Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341969#M72650</link>
      <description>run the ssh clients and deamon in debug ( -dd )</description>
      <pubDate>Tue, 27 Jul 2004 09:26:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341969#M72650</guid>
      <dc:creator>Olivier Drouin</dc:creator>
      <dc:date>2004-07-27T09:26:18Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341970#M72651</link>
      <description>check the permission on .ssh directory .Only the owner should have the permissions.If the permission is too open -there's a problem</description>
      <pubDate>Tue, 27 Jul 2004 09:30:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341970#M72651</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2004-07-27T09:30:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341971#M72652</link>
      <description>I'll give the -dd a try, that might give me some leads.&lt;BR /&gt;&lt;BR /&gt;Many Thanks&lt;BR /&gt;</description>
      <pubDate>Tue, 27 Jul 2004 09:32:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341971#M72652</guid>
      <dc:creator>Matt Palmer_2</dc:creator>
      <dc:date>2004-07-27T09:32:21Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341972#M72653</link>
      <description>Well, few more hints.. may be helpful.&lt;BR /&gt;1. By any chance did you copy-paste the key on the other server instead of actually sftp/scp-ing?&lt;BR /&gt;2. Are you running the exact same version of ssh on both servers? Check ssh -V on both. If the versions are different, there are some addiional steps required to export/import the keys.&lt;BR /&gt;3. Check to see if there is any differences between the /etc/ssh/sshd_config files.&lt;BR /&gt;4. Try to authentciate without ssh-agent initially, just using the keys on the file instead to see if that works.&lt;BR /&gt;5. If none works, post the poutput of sshd debug log as well as ssh -vvv (connection log)&lt;BR /&gt;&lt;BR /&gt;regds,&lt;BR /&gt;abdul.</description>
      <pubDate>Tue, 27 Jul 2004 11:55:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341972#M72653</guid>
      <dc:creator>Abdul Rahiman</dc:creator>
      <dc:date>2004-07-27T11:55:53Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341973#M72654</link>
      <description>Attached is a word doc. You can bypass the X part and use cat, but pay special attention to permissions in the doc.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 27 Jul 2004 14:24:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341973#M72654</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-07-27T14:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341974#M72655</link>
      <description>When you generated the keys using 'ssh-keygen', did you put in a password?&lt;BR /&gt;&lt;BR /&gt;Also, did you use 'ssh-agent' on both sides?&lt;BR /&gt;&lt;BR /&gt;If you put a password in when generating the keys, you will always be prompted for it, unless you use 'ssh-agent' (which is a password-cache for known keys basically).</description>
      <pubDate>Tue, 27 Jul 2004 18:44:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341974#M72655</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-07-27T18:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341975#M72656</link>
      <description>Hi Everyone,&lt;BR /&gt;&lt;BR /&gt;I've cracked it!! thanks for all the help. In the end after verbosing the o/p, the key auth was not getting processed because the directory permissions on the home directory for the user on the remote box were not 755 so the connection was not allowed. -Even though the .ssh directory inside there was fine.&lt;BR /&gt;&lt;BR /&gt;So changed file perms and now everything is fine&lt;BR /&gt;&lt;BR /&gt;Many Thanks&lt;BR /&gt;&lt;BR /&gt;Matt</description>
      <pubDate>Wed, 28 Jul 2004 05:38:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341975#M72656</guid>
      <dc:creator>Matt Palmer_2</dc:creator>
      <dc:date>2004-07-28T05:38:11Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341976#M72657</link>
      <description>Hm,&lt;BR /&gt;the permissions on home directory shouldn't be 755 for this purpose (it works perfectly even when the permission is 700).&lt;BR /&gt;It's the permission on .ssh folder that matters.It shouldn't be too open, i.e. granting 777 will prompt for password,755 however will alow passwordless login.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best regards.</description>
      <pubDate>Wed, 28 Jul 2004 06:18:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341976#M72657</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2004-07-28T06:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: SSH keygen auth problems</title>
      <link>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341977#M72658</link>
      <description>All the permission from "/" up to "~/.ssh" are important.&lt;BR /&gt;&lt;BR /&gt;If .ssh is 700 but your home directory is 777 it will ask for a passwd.</description>
      <pubDate>Wed, 28 Jul 2004 07:27:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/ssh-keygen-auth-problems/m-p/3341977#M72658</guid>
      <dc:creator>Olivier Drouin</dc:creator>
      <dc:date>2004-07-28T07:27:52Z</dc:date>
    </item>
  </channel>
</rss>

