<?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 Re: SSH authorized_keys file in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106444#M147908</link>
    <description>"The authorized_keys file contains the public keys from other user accounts.&lt;BR /&gt;The user must put their public key in this authorization file. Only add the&lt;BR /&gt;public key of other user accounts that you want to be able to access your&lt;BR /&gt;account. Typically you are only adding your own public key from another&lt;BR /&gt;system. A user could copy the file over and rename, but be careful as this&lt;BR /&gt;file may contain multiple public keys, in which case you would want to&lt;BR /&gt;append to the file.&lt;BR /&gt;In HP-SSH the default name for the authorized_keys file can be found in the&lt;BR /&gt;sshd_config file:&lt;BR /&gt;#AuthorizedKeysFile .ssh/authorized_keys&lt;BR /&gt;In some implementations the name authorized_keys2 is used for the SSH-2&lt;BR /&gt;protocol."  (from Chris Wong's ssh explained)&lt;BR /&gt;&lt;BR /&gt;I'd attach the whole pdf but it goes for 2Mb.&lt;BR /&gt;Pick one here : &lt;A href="http://www.newfdawg.com/docs/HP-SSH_Explained.PDF" target="_blank"&gt;http://www.newfdawg.com/docs/HP-SSH_Explained.PDF&lt;/A&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 30 Oct 2003 10:29:47 GMT</pubDate>
    <dc:creator>Zeev Schultz</dc:creator>
    <dc:date>2003-10-30T10:29:47Z</dc:date>
    <item>
      <title>SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106442#M147906</link>
      <description>While doing some research on a problem, I discovered my authorized_keys files are likly not built correctly. The Definitive Guide book does not have concrete examples of the structure  of the file that I can find.  Does anyone know where I can get more / better examples on the file?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Rt.</description>
      <pubDate>Thu, 30 Oct 2003 09:50:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106442#M147906</guid>
      <dc:creator>Robert True</dc:creator>
      <dc:date>2003-10-30T09:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106443#M147907</link>
      <description>This is not something you build manually.&lt;BR /&gt;&lt;BR /&gt;If its corrupt, erase it and it will be rebuilt correctly as you do ssh connections to other systems.&lt;BR /&gt;&lt;BR /&gt;The word doc I'm attaching briefly discusses a proceess that builds them.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 30 Oct 2003 10:24:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106443#M147907</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-10-30T10:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106444#M147908</link>
      <description>"The authorized_keys file contains the public keys from other user accounts.&lt;BR /&gt;The user must put their public key in this authorization file. Only add the&lt;BR /&gt;public key of other user accounts that you want to be able to access your&lt;BR /&gt;account. Typically you are only adding your own public key from another&lt;BR /&gt;system. A user could copy the file over and rename, but be careful as this&lt;BR /&gt;file may contain multiple public keys, in which case you would want to&lt;BR /&gt;append to the file.&lt;BR /&gt;In HP-SSH the default name for the authorized_keys file can be found in the&lt;BR /&gt;sshd_config file:&lt;BR /&gt;#AuthorizedKeysFile .ssh/authorized_keys&lt;BR /&gt;In some implementations the name authorized_keys2 is used for the SSH-2&lt;BR /&gt;protocol."  (from Chris Wong's ssh explained)&lt;BR /&gt;&lt;BR /&gt;I'd attach the whole pdf but it goes for 2Mb.&lt;BR /&gt;Pick one here : &lt;A href="http://www.newfdawg.com/docs/HP-SSH_Explained.PDF" target="_blank"&gt;http://www.newfdawg.com/docs/HP-SSH_Explained.PDF&lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2003 10:29:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106444#M147908</guid>
      <dc:creator>Zeev Schultz</dc:creator>
      <dc:date>2003-10-30T10:29:47Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106445#M147909</link>
      <description>copy your .pub files you create on other systems to the .ssh/authorized_keys file. This will allow you to use your passphrases you entered when you ran ssh-keygen on the client. This file is very picky on syntax, make sure there are no extra spaces at the end of your keys.&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2003 10:49:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106445#M147909</guid>
      <dc:creator>Kevin Wright</dc:creator>
      <dc:date>2003-10-30T10:49:43Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106446#M147910</link>
      <description>Steven: I think you were thinking of the known_hosts file, which does get generated automaticly (or at least semi-automaticly: on my system it is set to ask).  I hope an authorized_keys file will not be generated automaticly!&lt;BR /&gt;&lt;BR /&gt;The doc you pointed to, while confusing and hard to read, does discribe a method of building an authorized_keys file, but not exactly what I am looking for.&lt;BR /&gt;&lt;BR /&gt;Zeev: The newfldawg pdf doc you pointed to does contain some interesting view graphs. Thanks.&lt;BR /&gt;&lt;BR /&gt;To clarify, what I am looking for is: the syntax of the optional authorization entries for a key, such as allowing port-forwarding, restricting to a specific host, subnet,domain, etc.  The above mentioned Def. Guide is confusing me as to the syntax for HP's version of the file.&lt;BR /&gt;&lt;BR /&gt;Rt. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2003 12:54:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106446#M147910</guid>
      <dc:creator>Robert True</dc:creator>
      <dc:date>2003-10-30T12:54:52Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106447#M147911</link>
      <description>You were right.&lt;BR /&gt;&lt;BR /&gt;In actuality, the document I provided was much more relavent.&lt;BR /&gt;&lt;BR /&gt;Rebuild your known_hosts public key files according to Chris Vail's doc.  I don't use xwindows any more, I just use the cat command, but that will rebuild the file for you.&lt;BR /&gt;&lt;BR /&gt;You have to have the known_hosts built up to get useful public keys in authorized_keys&lt;BR /&gt;&lt;BR /&gt;Once authorized_keys is messed up there is no point in trying to edit or recovery, just do it over.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 30 Oct 2003 12:59:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106447#M147911</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-10-30T12:59:54Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106448#M147912</link>
      <description>I've seen authorized_keys files corrupted when public keys are copy/pasted into them.  Each key should be a single continuous line.  Copying and pasting can insert unwanted CR-LF's into these files.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Oct 2003 18:43:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106448#M147912</guid>
      <dc:creator>James A. Donovan</dc:creator>
      <dc:date>2003-10-30T18:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106449#M147913</link>
      <description>port forwarding, host, subnet, domain restrictions, etc. are all controlled by the settings in the sshd_config file, not the authorized_keys file.&lt;BR /&gt;&lt;BR /&gt;Take a look at the man page for sshd_config:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config&amp;amp;sektion=5&amp;amp;arch=&amp;amp;apropos=0&amp;amp;manpath=OpenBSD+Current" target="_blank"&gt;http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config&amp;amp;sektion=5&amp;amp;arch=&amp;amp;apropos=0&amp;amp;manpath=OpenBSD+Current&lt;/A&gt;</description>
      <pubDate>Thu, 30 Oct 2003 18:53:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106449#M147913</guid>
      <dc:creator>James A. Donovan</dc:creator>
      <dc:date>2003-10-30T18:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106450#M147914</link>
      <description>Hello Robert,&lt;BR /&gt;&lt;BR /&gt;Refer to the foll. links for info.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.lbl.gov/ITSD/CIS/faqs/SOFTWARE_Data_Communications/2.html" target="_blank"&gt;http://www.lbl.gov/ITSD/CIS/faqs/SOFTWARE_Data_Communications/2.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://newfdawg.com/SHP-SSHpart4.htm" target="_blank"&gt;http://newfdawg.com/SHP-SSHpart4.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.trustix.org/pipermail/tsl-discuss/2001-October/001398.html" target="_blank"&gt;http://www.trustix.org/pipermail/tsl-discuss/2001-October/001398.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;HTH.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Hemanth</description>
      <pubDate>Thu, 30 Oct 2003 22:31:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106450#M147914</guid>
      <dc:creator>Hemanth Gurunath Basrur</dc:creator>
      <dc:date>2003-10-30T22:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: SSH authorized_keys file</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106451#M147915</link>
      <description>Thanks everyone, but my keys are working fine, nothing is corrupted, I use ssh only for all communication between systems I administer.&lt;BR /&gt;&lt;BR /&gt;I am trying to  do some fine tuning on individual accounts as OReilly's Def. Guide seems to imply can be done for various situations, ie: run single commands, restrict to defined locations, etc.&lt;BR /&gt;&lt;BR /&gt;The last link supplied to newfdawg makes me think I should spend some more time there, as I have not been on there much in a long while.&lt;BR /&gt;&lt;BR /&gt;Thanks again,&lt;BR /&gt;Rt.</description>
      <pubDate>Fri, 31 Oct 2003 09:38:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ssh-authorized-keys-file/m-p/3106451#M147915</guid>
      <dc:creator>Robert True</dc:creator>
      <dc:date>2003-10-31T09:38:44Z</dc:date>
    </item>
  </channel>
</rss>

