<?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: Ftam &amp;amp; shadowpassword in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-amp-shadowpassword/m-p/3670807#M243713</link>
    <description>This might take quite a lot of work, but I think it might be possible to chroot the FTAM application if there is no easier way to solve your problem.&lt;BR /&gt;&lt;BR /&gt;You would have to build a "stripped-down" directory hierarchy for FTAM: for example, if you choose /ftamjail as your chroot directory, you'd create /ftamjail/etc/passwd with just the  user accounts FTAM needs.&lt;BR /&gt;&lt;BR /&gt;Everything the application needs must be copied (not symlinked) inside the chroot: system libraries, configuration files (including DNS configuration files like /etc/hosts, /etc/resolv.conf and /etc/nsswitch.conf) and the binaries FTAM uses.&lt;BR /&gt;&lt;BR /&gt;Finally, you start the chrooted FTAM with a command like:&lt;BR /&gt;chroot /ftamjail the-command-to-start-FTAM&lt;BR /&gt;</description>
    <pubDate>Mon, 14 Nov 2005 07:08:16 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2005-11-14T07:08:16Z</dc:date>
    <item>
      <title>Ftam &amp; shadowpassword</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-amp-shadowpassword/m-p/3670806#M243712</link>
      <description>Hi!&lt;BR /&gt;&lt;BR /&gt;I know the combination is unsupported, but my system is in trusted mode and I can´t change it back in untrusted mode. &lt;BR /&gt;&lt;BR /&gt;Question is: Can I create other passwd file, which ftam uses or is there at all anything unsupport way to solve problem.</description>
      <pubDate>Mon, 14 Nov 2005 03:54:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftam-amp-shadowpassword/m-p/3670806#M243712</guid>
      <dc:creator>Jyrki Tounas</dc:creator>
      <dc:date>2005-11-14T03:54:09Z</dc:date>
    </item>
    <item>
      <title>Re: Ftam &amp; shadowpassword</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ftam-amp-shadowpassword/m-p/3670807#M243713</link>
      <description>This might take quite a lot of work, but I think it might be possible to chroot the FTAM application if there is no easier way to solve your problem.&lt;BR /&gt;&lt;BR /&gt;You would have to build a "stripped-down" directory hierarchy for FTAM: for example, if you choose /ftamjail as your chroot directory, you'd create /ftamjail/etc/passwd with just the  user accounts FTAM needs.&lt;BR /&gt;&lt;BR /&gt;Everything the application needs must be copied (not symlinked) inside the chroot: system libraries, configuration files (including DNS configuration files like /etc/hosts, /etc/resolv.conf and /etc/nsswitch.conf) and the binaries FTAM uses.&lt;BR /&gt;&lt;BR /&gt;Finally, you start the chrooted FTAM with a command like:&lt;BR /&gt;chroot /ftamjail the-command-to-start-FTAM&lt;BR /&gt;</description>
      <pubDate>Mon, 14 Nov 2005 07:08:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ftam-amp-shadowpassword/m-p/3670807#M243713</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2005-11-14T07:08:16Z</dc:date>
    </item>
  </channel>
</rss>

