<?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: Sudo Problems in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592011#M592945</link>
    <description>If you really think about it, there really is not way to secure something like sudo...there has to be some amount of trust.&lt;BR /&gt;&lt;BR /&gt;For example, there is nothing that prevents a user from doing something like the following:&lt;BR /&gt;&lt;BR /&gt;cp /bin/ksh /tmp/myksh&lt;BR /&gt;chown root:root /tmp/myksh&lt;BR /&gt;sudo chmod 4555 /tmp/myksh&lt;BR /&gt;&lt;BR /&gt;and now I have a ksh that has root privs.&lt;BR /&gt;&lt;BR /&gt;The only other alternative is to write a suid program (not a script) that only does a specific thing, such as a chown, but even then you'd have to do so many checks that you're probably going to give up in frustration. :-)&lt;BR /&gt;&lt;BR /&gt;-Santosh</description>
    <pubDate>Tue, 09 Oct 2001 19:15:47 GMT</pubDate>
    <dc:creator>Santosh Nair_1</dc:creator>
    <dc:date>2001-10-09T19:15:47Z</dc:date>
    <item>
      <title>Sudo Problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592009#M592943</link>
      <description>I was going about some sudo file maintanence this evening and found that if a user were to have sudo privliges to chmod or chown they could simply change their access or anyones access in the sudoers file simply by modifying their rights to the file. Does anyone have a solution for this?&lt;BR /&gt;&lt;BR /&gt;I could put it on an nfs drive and mount it as read only but that seems so cumbersome. There has to be a more viable solution.&lt;BR /&gt;&lt;BR /&gt;I know giving chmod / own rights to a user is a bad thing but it is necessary in this case. I guess giving them rights to chmod or chown at all gives them pretty much free run of the machines they are on. Maybe this is a no win situation.</description>
      <pubDate>Tue, 09 Oct 2001 19:04:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592009#M592943</guid>
      <dc:creator>Daniel Crow</dc:creator>
      <dc:date>2001-10-09T19:04:31Z</dc:date>
    </item>
    <item>
      <title>Re: Sudo Problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592010#M592944</link>
      <description>especially if they did this:&lt;BR /&gt;&lt;BR /&gt;cp /usr/bin/ksh myksh&lt;BR /&gt;chown root bin myksh&lt;BR /&gt;chmod 4777 myksh&lt;BR /&gt;&lt;BR /&gt;then they could always have a "root" user, without sudo!</description>
      <pubDate>Tue, 09 Oct 2001 19:11:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592010#M592944</guid>
      <dc:creator>harry d brown jr</dc:creator>
      <dc:date>2001-10-09T19:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Sudo Problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592011#M592945</link>
      <description>If you really think about it, there really is not way to secure something like sudo...there has to be some amount of trust.&lt;BR /&gt;&lt;BR /&gt;For example, there is nothing that prevents a user from doing something like the following:&lt;BR /&gt;&lt;BR /&gt;cp /bin/ksh /tmp/myksh&lt;BR /&gt;chown root:root /tmp/myksh&lt;BR /&gt;sudo chmod 4555 /tmp/myksh&lt;BR /&gt;&lt;BR /&gt;and now I have a ksh that has root privs.&lt;BR /&gt;&lt;BR /&gt;The only other alternative is to write a suid program (not a script) that only does a specific thing, such as a chown, but even then you'd have to do so many checks that you're probably going to give up in frustration. :-)&lt;BR /&gt;&lt;BR /&gt;-Santosh</description>
      <pubDate>Tue, 09 Oct 2001 19:15:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592011#M592945</guid>
      <dc:creator>Santosh Nair_1</dc:creator>
      <dc:date>2001-10-09T19:15:47Z</dc:date>
    </item>
    <item>
      <title>Re: Sudo Problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592012#M592946</link>
      <description>I am not sure why I can't get it to work in this case, but for instance, to give users perms to change other users passwords and NOT roots, you do this..&lt;BR /&gt;users   passwd, !passwd root&lt;BR /&gt;&lt;BR /&gt;but&lt;BR /&gt;users   chown,  !chown /opt/sudo&lt;BR /&gt;does not seem to work.&lt;BR /&gt;&lt;BR /&gt;This is the only way I know of to restrict what sudo commands do.</description>
      <pubDate>Tue, 09 Oct 2001 20:43:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sudo-problems/m-p/2592012#M592946</guid>
      <dc:creator>Kevin Wright</dc:creator>
      <dc:date>2001-10-09T20:43:56Z</dc:date>
    </item>
  </channel>
</rss>

