<?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: different account  within the scripts in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126873#M748036</link>
    <description>Alternatively, you could install the 'other program' as a setuid or setgid binary using the chmod command.  But as Chris suggests, there are many security issues to consider here.  It's easy to give you a solution that would be functional.  We would have to know a lot more about your specific environment and needs to give you something that might be acceptable from a security point of view.&lt;BR /&gt;</description>
    <pubDate>Tue, 25 Nov 2003 05:27:31 GMT</pubDate>
    <dc:creator>doug hosking</dc:creator>
    <dc:date>2003-11-25T05:27:31Z</dc:date>
    <item>
      <title>different account  within the scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126871#M748034</link>
      <description>Hi!&lt;BR /&gt;  &lt;BR /&gt;   Is there a way to used the other account within the scipts that will call another program and also without prompting a password.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 24 Nov 2003 01:18:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126871#M748034</guid>
      <dc:creator>Jay C. Quibuloy</dc:creator>
      <dc:date>2003-11-24T01:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: different account  within the scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126872#M748035</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;if you start the script as user root you can run a script without prompting a password:&lt;BR /&gt;&lt;BR /&gt;&amp;lt;script&amp;gt;&lt;BR /&gt;su - &lt;USER&gt; -c &lt;PROGRAM&gt;&lt;BR /&gt;&amp;lt;script&amp;gt;&lt;BR /&gt;&lt;BR /&gt;the "su -" means that you source /etc/profile and .profile, so you have the environment from the user. In this files you must not have any programs that produce an output.&lt;BR /&gt;&lt;BR /&gt;Another way:&lt;BR /&gt;&lt;BR /&gt;&amp;lt;script&amp;gt;&lt;BR /&gt;su - user &amp;lt;&lt;EOFUSER&gt;&lt;/EOFUSER&gt;&lt;COMMAND&gt;&lt;BR /&gt;&lt;NEXT command=""&gt;&lt;BR /&gt;EOFUSER&lt;BR /&gt;&amp;lt;script&amp;gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;If you are not root it's not so easy.&lt;BR /&gt;&lt;BR /&gt;user1 want to run a program from user2:&lt;BR /&gt;you need a file &lt;BR /&gt;&lt;HOME from="" user2=""&gt;/.rhosts&lt;BR /&gt;with entry &lt;BR /&gt;&lt;HOSTNAME&gt; user1&lt;BR /&gt;&lt;BR /&gt;user1 can now "login" to user2 without password:&lt;BR /&gt;&amp;lt;script&amp;gt;&lt;BR /&gt;rexec hostname -l user2 &lt;COMMAND&gt;&lt;BR /&gt;&amp;lt;script&amp;gt;&lt;BR /&gt;Think of security !!!&lt;BR /&gt;&lt;BR /&gt;The same trick you can do with ssh and empty passphrase.&lt;BR /&gt;&lt;BR /&gt;Chris&lt;BR /&gt;&lt;/COMMAND&gt;&lt;/HOSTNAME&gt;&lt;/HOME&gt;&lt;/NEXT&gt;&lt;/COMMAND&gt;&lt;/PROGRAM&gt;&lt;/USER&gt;</description>
      <pubDate>Mon, 24 Nov 2003 03:04:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126872#M748035</guid>
      <dc:creator>Christian Gebhardt</dc:creator>
      <dc:date>2003-11-24T03:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: different account  within the scripts</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126873#M748036</link>
      <description>Alternatively, you could install the 'other program' as a setuid or setgid binary using the chmod command.  But as Chris suggests, there are many security issues to consider here.  It's easy to give you a solution that would be functional.  We would have to know a lot more about your specific environment and needs to give you something that might be acceptable from a security point of view.&lt;BR /&gt;</description>
      <pubDate>Tue, 25 Nov 2003 05:27:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/different-account-within-the-scripts/m-p/3126873#M748036</guid>
      <dc:creator>doug hosking</dc:creator>
      <dc:date>2003-11-25T05:27:31Z</dc:date>
    </item>
  </channel>
</rss>

