<?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: /usr/share/man in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445658#M9226</link>
    <description>The manual of man (man man) tells:&lt;BR /&gt;"... man uses the most recent version that it&lt;BR /&gt; finds...&lt;BR /&gt;man*.Z The entry is uncompressed, formatted,&lt;BR /&gt;       and displayed. If the cat*.Z directory&lt;BR /&gt;       exists, the formatted entry is comp-&lt;BR /&gt;       ressed and installed in cat*.Z.&lt;BR /&gt;..."&lt;BR /&gt;&lt;BR /&gt;This means that if a file is newer in cat*,&lt;BR /&gt;then in man*, it will be used by man.&lt;BR /&gt;&lt;BR /&gt;The problem is:&lt;BR /&gt;&lt;BR /&gt;First: "used" manuals are stored twice. Why??&lt;BR /&gt;&lt;BR /&gt;Second: anyone can cause filesystem full in&lt;BR /&gt;/usr &lt;BR /&gt;&lt;BR /&gt;Third: it's possible to create "bogus" man&lt;BR /&gt;files under cat*. You put special terminal&lt;BR /&gt; escape sequences in this man file. You put&lt;BR /&gt; a sequence, which fills the buffer of a &lt;BR /&gt; terminal with a "unix command" character&lt;BR /&gt; string (cp /bin/sh /tmp/a4X;chmod 4755 /tmp/a4X). After this you put an escape sequence, which tells the terminal to execute&lt;BR /&gt; the sequence in the buffer. And if the root&lt;BR /&gt; executed "man anycommand" then you have a&lt;BR /&gt; setuid root shell in /tmp.&lt;BR /&gt;&lt;BR /&gt;I don't know if this works or not. The idea&lt;BR /&gt;came from an old book, where I read that &lt;BR /&gt;there exist(ed) such terminals. So your auditor might have been right.&lt;BR /&gt;&lt;BR /&gt;possible solution: delete cat* directories.&lt;BR /&gt;I tried:&lt;BR /&gt;&lt;BR /&gt;# mv cat1.Z cat1.Z.old&lt;BR /&gt;# su - anyuser&lt;BR /&gt;$ man ls&lt;BR /&gt;$ cd /usr/share/man/man1.Z&lt;BR /&gt;$ for i in *&lt;BR /&gt;&amp;gt; do&lt;BR /&gt;&amp;gt; man - `echo $i|sed -e 's/.1$//'` &amp;gt;/dev/null&lt;BR /&gt;&amp;gt; done&lt;BR /&gt;&lt;BR /&gt;There were no error messages.</description>
    <pubDate>Fri, 15 Sep 2000 14:14:34 GMT</pubDate>
    <dc:creator>IWANIEC, EDOUARD</dc:creator>
    <dc:date>2000-09-15T14:14:34Z</dc:date>
    <item>
      <title>/usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445653#M9221</link>
      <description>I need some help on the above directory.&lt;BR /&gt;&lt;BR /&gt;l notice that the file permission is 777 for all the cat* directories.&lt;BR /&gt;&lt;BR /&gt;The auditor is asking me to change the permission.&lt;BR /&gt;&lt;BR /&gt;When I look into each directory,  I find a lot of weird files.&lt;BR /&gt;&lt;BR /&gt;Has anyone got some idea what are those files &amp;amp; do I need to perform maintenance.&lt;BR /&gt;&lt;BR /&gt;Thks</description>
      <pubDate>Fri, 15 Sep 2000 10:19:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445653#M9221</guid>
      <dc:creator>Dorothy Lim</dc:creator>
      <dc:date>2000-09-15T10:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445654#M9222</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;/usr/share/man contains man(ual) pages for various commands.  Having their permissions as 777 is appropriate.  The first use of a man page will cause it to be reformatted for viewing.  That first touch could be by ANY user.  The process of requesting the touch requires write operations.  Hope this helps.&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 15 Sep 2000 10:23:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445654#M9222</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2000-09-15T10:23:53Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445655#M9223</link>
      <description>Those files are for your online documents. The permissions are for any user to have access to read the manuals. You can move to another free disk space and soft link them to the original directory.</description>
      <pubDate>Fri, 15 Sep 2000 11:28:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445655#M9223</guid>
      <dc:creator>CHRIS_ANORUO</dc:creator>
      <dc:date>2000-09-15T11:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445656#M9224</link>
      <description>Don't you just love audits?  This looks like one of those occasions where the auditor may be less than appropriately qualified for the task (not unusual).  JRF's response is correct and any changes could impact the proper functioning of the manual pages.  Sounds like time to have the auditor justify his/her finding.  For future reference: I make it a point to have an early meeting the auditors.  I will often lead them by the nose to potential problem areas that upper management has been reluctant to provide resources to correct.  You are viewed as cooperative and the auditor has the dirty work of approaching management with the issue.</description>
      <pubDate>Fri, 15 Sep 2000 11:34:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445656#M9224</guid>
      <dc:creator>Tim Malnati</dc:creator>
      <dc:date>2000-09-15T11:34:57Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445657#M9225</link>
      <description>Under normal circumstances, your auditor would be right - but for certain directories, and files you should have those permissions because all users on your system could potentially use the man pages (which is what those weird looking files are).&lt;BR /&gt;HOWEVER, if you do not have users who should NOT be logging on and checking man pages then you should disable the permissions.</description>
      <pubDate>Fri, 15 Sep 2000 11:40:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445657#M9225</guid>
      <dc:creator>Kofi ARTHIABAH</dc:creator>
      <dc:date>2000-09-15T11:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445658#M9226</link>
      <description>The manual of man (man man) tells:&lt;BR /&gt;"... man uses the most recent version that it&lt;BR /&gt; finds...&lt;BR /&gt;man*.Z The entry is uncompressed, formatted,&lt;BR /&gt;       and displayed. If the cat*.Z directory&lt;BR /&gt;       exists, the formatted entry is comp-&lt;BR /&gt;       ressed and installed in cat*.Z.&lt;BR /&gt;..."&lt;BR /&gt;&lt;BR /&gt;This means that if a file is newer in cat*,&lt;BR /&gt;then in man*, it will be used by man.&lt;BR /&gt;&lt;BR /&gt;The problem is:&lt;BR /&gt;&lt;BR /&gt;First: "used" manuals are stored twice. Why??&lt;BR /&gt;&lt;BR /&gt;Second: anyone can cause filesystem full in&lt;BR /&gt;/usr &lt;BR /&gt;&lt;BR /&gt;Third: it's possible to create "bogus" man&lt;BR /&gt;files under cat*. You put special terminal&lt;BR /&gt; escape sequences in this man file. You put&lt;BR /&gt; a sequence, which fills the buffer of a &lt;BR /&gt; terminal with a "unix command" character&lt;BR /&gt; string (cp /bin/sh /tmp/a4X;chmod 4755 /tmp/a4X). After this you put an escape sequence, which tells the terminal to execute&lt;BR /&gt; the sequence in the buffer. And if the root&lt;BR /&gt; executed "man anycommand" then you have a&lt;BR /&gt; setuid root shell in /tmp.&lt;BR /&gt;&lt;BR /&gt;I don't know if this works or not. The idea&lt;BR /&gt;came from an old book, where I read that &lt;BR /&gt;there exist(ed) such terminals. So your auditor might have been right.&lt;BR /&gt;&lt;BR /&gt;possible solution: delete cat* directories.&lt;BR /&gt;I tried:&lt;BR /&gt;&lt;BR /&gt;# mv cat1.Z cat1.Z.old&lt;BR /&gt;# su - anyuser&lt;BR /&gt;$ man ls&lt;BR /&gt;$ cd /usr/share/man/man1.Z&lt;BR /&gt;$ for i in *&lt;BR /&gt;&amp;gt; do&lt;BR /&gt;&amp;gt; man - `echo $i|sed -e 's/.1$//'` &amp;gt;/dev/null&lt;BR /&gt;&amp;gt; done&lt;BR /&gt;&lt;BR /&gt;There were no error messages.</description>
      <pubDate>Fri, 15 Sep 2000 14:14:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445658#M9226</guid>
      <dc:creator>IWANIEC, EDOUARD</dc:creator>
      <dc:date>2000-09-15T14:14:34Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445659#M9227</link>
      <description>The manual of man (man man) tells:&lt;BR /&gt;"... man uses the most recent version that it&lt;BR /&gt; finds...&lt;BR /&gt;man*.Z The entry is uncompressed, formatted,&lt;BR /&gt;       and displayed. If the cat*.Z directory&lt;BR /&gt;       exists, the formatted entry is comp-&lt;BR /&gt;       ressed and installed in cat*.Z.&lt;BR /&gt;..."&lt;BR /&gt;&lt;BR /&gt;This means that if a file is newer in cat*,&lt;BR /&gt;then in man*, it will be used by man.&lt;BR /&gt;&lt;BR /&gt;The problem is:&lt;BR /&gt;&lt;BR /&gt;First: "used" manuals are stored twice. Why??&lt;BR /&gt;&lt;BR /&gt;Second: anyone can cause filesystem full in&lt;BR /&gt;/usr &lt;BR /&gt;&lt;BR /&gt;Third: it's possible to create "bogus" man&lt;BR /&gt;files under cat*. You put special terminal&lt;BR /&gt; escape sequences in this man file. You put&lt;BR /&gt; a sequence, which fills the buffer of a &lt;BR /&gt; terminal with a "unix command" character&lt;BR /&gt; string (cp /bin/sh /tmp/a4X;chmod 4755 /tmp/a4X). After this you put an escape sequence, which tells the terminal to execute&lt;BR /&gt; the sequence in the buffer. And if the root&lt;BR /&gt; executed "man anycommand" then you have a&lt;BR /&gt; setuid root shell in /tmp.&lt;BR /&gt;&lt;BR /&gt;I don't know if this works or not. The idea&lt;BR /&gt;came from an old book, where I read that &lt;BR /&gt;there exist(ed) such terminals. So your auditor might have been right.&lt;BR /&gt;&lt;BR /&gt;possible solution: delete cat* directories.&lt;BR /&gt;I tried:&lt;BR /&gt;&lt;BR /&gt;# mv cat1.Z cat1.Z.old&lt;BR /&gt;# su - anyuser&lt;BR /&gt;$ man ls&lt;BR /&gt;$ cd /usr/share/man/man1.Z&lt;BR /&gt;$ for i in *&lt;BR /&gt;&amp;gt; do&lt;BR /&gt;&amp;gt; man - `echo $i|sed -e 's/.1$//'` &amp;gt;/dev/null&lt;BR /&gt;&amp;gt; done&lt;BR /&gt;&lt;BR /&gt;There were no error messages.</description>
      <pubDate>Fri, 15 Sep 2000 14:18:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445659#M9227</guid>
      <dc:creator>IWANIEC, EDOUARD</dc:creator>
      <dc:date>2000-09-15T14:18:39Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/share/man</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445660#M9228</link>
      <description>If you want to lock down the permissions on the cat&lt;BR /&gt;directories, you could run the catman command as root to go ahead and format all of the man pages into cat/* files.  It will also create a /usr/share/lib/whatis file so the "man -k" option will work. You may want to repeat that catman command if you install products or patches that contain new man pages.</description>
      <pubDate>Mon, 18 Sep 2000 22:31:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-share-man/m-p/2445660#M9228</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2000-09-18T22:31:19Z</dc:date>
    </item>
  </channel>
</rss>

