<?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: Limit a user to a single program in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564073#M919263</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;here an unsupported procedure:&lt;BR /&gt;&lt;BR /&gt;Change in /usr/dt/bin/Xsession the lines:&lt;BR /&gt;&lt;BR /&gt;dtstart_session[0]="$DT_BINPATH/dtsession"&lt;BR /&gt;dtstart_session[1]="$HOME/.xsession"&lt;BR /&gt;&lt;BR /&gt;to&lt;BR /&gt;&lt;BR /&gt;dtstart_session[1]="$DT_BINPATH/dtsession"&lt;BR /&gt;dtstart_session[0]="$HOME/.xsession"&lt;BR /&gt;&lt;BR /&gt;(this will change the order for Xsession for looking what session has to be started)&lt;BR /&gt;&lt;BR /&gt;Now you have to create a file $HOME/.xsession in the user home directory with executable rights (chmod 755 $HOME/.xsession)&lt;BR /&gt;&lt;BR /&gt;Copy /usr/dt/config/Xfailsave to $HOME/.xsession.&lt;BR /&gt;&lt;BR /&gt;Within $HOME/.xsession change the line&lt;BR /&gt;&lt;BR /&gt;${CDEDIR}/dtterm -ls&lt;BR /&gt;&lt;BR /&gt;to your needs (your X-application should be started here).&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;</description>
    <pubDate>Fri, 10 Aug 2001 08:19:03 GMT</pubDate>
    <dc:creator>Andreas Voss</dc:creator>
    <dc:date>2001-08-10T08:19:03Z</dc:date>
    <item>
      <title>Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564071#M919261</link>
      <description>On a HP-UX 10.20/11 system (with CDE), how can I limit a user to the execution of a single program.&lt;BR /&gt;&lt;BR /&gt;This programs should be launched each time the user logs in (with CDE login screen or with telnet/rlogin/su command). It should be the only program available to the user (no Xterm, no CDE pannel, no other program...).&lt;BR /&gt;&lt;BR /&gt;When the user exits the program, the Unix session should exit too.&lt;BR /&gt;&lt;BR /&gt;Note that the program is a graphical program so if cannot execute (for instance, because DISPLAY is not set, or because terminal screen is not graphical), Unix session should exit immediatly.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Tristan Savalle</description>
      <pubDate>Fri, 10 Aug 2001 07:39:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564071#M919261</guid>
      <dc:creator>Tristan Savalle</dc:creator>
      <dc:date>2001-08-10T07:39:40Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564072#M919262</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You could try setting their login shell to be a wrapper script that, say, performs some environment checks, runs the program, then it will exit at the end and log the user out.&lt;BR /&gt;&lt;BR /&gt;Rgds, Robin</description>
      <pubDate>Fri, 10 Aug 2001 07:50:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564072#M919262</guid>
      <dc:creator>Robin Wakefield</dc:creator>
      <dc:date>2001-08-10T07:50:49Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564073#M919263</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;here an unsupported procedure:&lt;BR /&gt;&lt;BR /&gt;Change in /usr/dt/bin/Xsession the lines:&lt;BR /&gt;&lt;BR /&gt;dtstart_session[0]="$DT_BINPATH/dtsession"&lt;BR /&gt;dtstart_session[1]="$HOME/.xsession"&lt;BR /&gt;&lt;BR /&gt;to&lt;BR /&gt;&lt;BR /&gt;dtstart_session[1]="$DT_BINPATH/dtsession"&lt;BR /&gt;dtstart_session[0]="$HOME/.xsession"&lt;BR /&gt;&lt;BR /&gt;(this will change the order for Xsession for looking what session has to be started)&lt;BR /&gt;&lt;BR /&gt;Now you have to create a file $HOME/.xsession in the user home directory with executable rights (chmod 755 $HOME/.xsession)&lt;BR /&gt;&lt;BR /&gt;Copy /usr/dt/config/Xfailsave to $HOME/.xsession.&lt;BR /&gt;&lt;BR /&gt;Within $HOME/.xsession change the line&lt;BR /&gt;&lt;BR /&gt;${CDEDIR}/dtterm -ls&lt;BR /&gt;&lt;BR /&gt;to your needs (your X-application should be started here).&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Aug 2001 08:19:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564073#M919263</guid>
      <dc:creator>Andreas Voss</dc:creator>
      <dc:date>2001-08-10T08:19:03Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564074#M919264</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;My simple way could be put exec statement in .profile of user.&lt;BR /&gt;&lt;BR /&gt;Let say user has to run xyz.exe, then last line of .profile of user should be &lt;BR /&gt;exec xyz.exe&lt;BR /&gt;&lt;BR /&gt;So when he logs in it will directly go to program and when he comes out of that program, it logs him out.&lt;BR /&gt;&lt;BR /&gt;Hope this may help u.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Joe.</description>
      <pubDate>Fri, 10 Aug 2001 09:05:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564074#M919264</guid>
      <dc:creator>Joseph Chakkery</dc:creator>
      <dc:date>2001-08-10T09:05:53Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564075#M919265</link>
      <description>I tend to use the quick &amp;amp; easy method that Joseph mentioned.  &lt;BR /&gt;I simply put the exec for what program I want them to run upon login into the users .profile...and I also add the command exit on the next line - so when they exit the program they are 'forced' out.&lt;BR /&gt;&lt;BR /&gt;/rcw&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Aug 2001 12:55:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564075#M919265</guid>
      <dc:creator>Rita C Workman</dc:creator>
      <dc:date>2001-08-10T12:55:04Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564076#M919266</link>
      <description>Hi Savalle,&lt;BR /&gt;&lt;BR /&gt;just put the absolute path of this program as the shell script to that user in /etc/passwd.&lt;BR /&gt;&lt;BR /&gt;you would also desactivate all interrupts in order that the user couldn't work arround what permissions you are setting.&lt;BR /&gt;&lt;BR /&gt;Magdi</description>
      <pubDate>Fri, 10 Aug 2001 13:04:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564076#M919266</guid>
      <dc:creator>Magdi KAMAL</dc:creator>
      <dc:date>2001-08-10T13:04:04Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564077#M919267</link>
      <description>We have done the previous suggestion of executing the comman in the .profile.  I would suggest trapping for errors in the .profile as well to prevent users from bypassing the controls you have in place (such as by pressing ctrl-c while the .profile is executing).  I would just put the following command at the beginning of the .profile:&lt;BR /&gt;trap "echo error; exit 1" 1 2 3 4 5 6&lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Fri, 10 Aug 2001 17:55:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564077#M919267</guid>
      <dc:creator>Andrew Maslin</dc:creator>
      <dc:date>2001-08-10T17:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: Limit a user to a single program</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564078#M919268</link>
      <description>The above is good!!!  Another thing to consider is that puting exit at the end of the .profile will not exit cde if you are not sourcing it.  In the $HOME/.dtprofile make sure (usually the last line) states DTSOURCEPROFILE=TRUE.  This forces cde to read the .profile.&lt;BR /&gt;&lt;BR /&gt;As far as su????????  This will not work.  However, the user should not have another account from which he can su.  If he/she does, you should do the same with that account.&lt;BR /&gt;&lt;BR /&gt;Also, I would chmod 755 $HOME/.profile $HOME/.dtprofile (assuming sh/ksh) and chown root:sys $HOME/.profile $HOME/.dtprofile.&lt;BR /&gt;&lt;BR /&gt;Another thing I would do is add the user to /etc/ftpd/ftpusers&lt;BR /&gt;&lt;BR /&gt;Just my thoughts.&lt;BR /&gt;&lt;BR /&gt;...jcd...</description>
      <pubDate>Fri, 10 Aug 2001 18:40:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/limit-a-user-to-a-single-program/m-p/2564078#M919268</guid>
      <dc:creator>Joseph C. Denman</dc:creator>
      <dc:date>2001-08-10T18:40:30Z</dc:date>
    </item>
  </channel>
</rss>

