<?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: rootsh and sudo problem in Secure OS Software for Linux</title>
    <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733822#M408</link>
    <description>You can audit the sudo related commands with history files itself generally.&lt;BR /&gt;&lt;BR /&gt;Another method as writing shell wrapper as,&lt;BR /&gt;&lt;BR /&gt;# mv &lt;BINARY sudo=""&gt; sudo.org&lt;BR /&gt;# cat &amp;gt; sudo&lt;BR /&gt;#!/bin/bash&lt;BR /&gt;if [[ $1 = "bash" ]]&lt;BR /&gt;then&lt;BR /&gt;  &lt;START rootsh=""&gt; # put the command to start&lt;BR /&gt;fi&lt;BR /&gt;echo $* | bash&lt;BR /&gt;&lt;BR /&gt;# end&lt;BR /&gt;exit 0&lt;BR /&gt;&lt;BR /&gt;###########&lt;BR /&gt;&lt;BR /&gt;Change permission to new sudo file and try now.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/START&gt;&lt;/BINARY&gt;</description>
    <pubDate>Fri, 17 Feb 2006 07:29:56 GMT</pubDate>
    <dc:creator>Muthukumar_5</dc:creator>
    <dc:date>2006-02-17T07:29:56Z</dc:date>
    <item>
      <title>rootsh and sudo problem</title>
      <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733821#M407</link>
      <description>Hallo all,&lt;BR /&gt;&lt;BR /&gt;I hope someone can help me with this problem.&lt;BR /&gt;&lt;BR /&gt;To make our servers more secure have stopped root access with su and the administartors have to SUDO to run root commands, that is working really well. I have also a logging-program called rootsh to log everything that are done as root, my problem is that to start the logging the admins then they have to "sudo rootsh" and they get a root shell with logging, but it is still possible to "sudo bash" and then they get a root-shell without logging. &lt;BR /&gt;&lt;BR /&gt;What I want is when they use "sudo bash", then the rootsh should be started automaticaly and logg what is happening.&lt;BR /&gt;&lt;BR /&gt;I have not manage to come up with a solution how to get this to work!&lt;BR /&gt;&lt;BR /&gt;Greatful for help!&lt;BR /&gt;&lt;BR /&gt;Cheers&lt;BR /&gt;Joppe</description>
      <pubDate>Fri, 17 Feb 2006 07:20:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733821#M407</guid>
      <dc:creator>Joppe</dc:creator>
      <dc:date>2006-02-17T07:20:22Z</dc:date>
    </item>
    <item>
      <title>Re: rootsh and sudo problem</title>
      <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733822#M408</link>
      <description>You can audit the sudo related commands with history files itself generally.&lt;BR /&gt;&lt;BR /&gt;Another method as writing shell wrapper as,&lt;BR /&gt;&lt;BR /&gt;# mv &lt;BINARY sudo=""&gt; sudo.org&lt;BR /&gt;# cat &amp;gt; sudo&lt;BR /&gt;#!/bin/bash&lt;BR /&gt;if [[ $1 = "bash" ]]&lt;BR /&gt;then&lt;BR /&gt;  &lt;START rootsh=""&gt; # put the command to start&lt;BR /&gt;fi&lt;BR /&gt;echo $* | bash&lt;BR /&gt;&lt;BR /&gt;# end&lt;BR /&gt;exit 0&lt;BR /&gt;&lt;BR /&gt;###########&lt;BR /&gt;&lt;BR /&gt;Change permission to new sudo file and try now.&lt;BR /&gt;&lt;BR /&gt;--&lt;BR /&gt;Muthu&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/START&gt;&lt;/BINARY&gt;</description>
      <pubDate>Fri, 17 Feb 2006 07:29:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733822#M408</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2006-02-17T07:29:56Z</dc:date>
    </item>
    <item>
      <title>Re: rootsh and sudo problem</title>
      <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733823#M409</link>
      <description>Thanks, that works fine!&lt;BR /&gt;But This means that I can't add new users to the sudoers file that I only want to let run a few specified commands.&lt;BR /&gt;&lt;BR /&gt;The question is if it is possible to have it so I still easy can add sudo rules for other users also? &lt;BR /&gt;&lt;BR /&gt;/Joppe</description>
      <pubDate>Fri, 17 Feb 2006 07:58:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733823#M409</guid>
      <dc:creator>Joppe</dc:creator>
      <dc:date>2006-02-17T07:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: rootsh and sudo problem</title>
      <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733824#M410</link>
      <description>Oups, was a little to fast to replay.&lt;BR /&gt;&lt;BR /&gt;With this script instead of the orginal sudo makes my logg file look like rubbish instead!&lt;BR /&gt;&lt;BR /&gt;/Joppe</description>
      <pubDate>Fri, 17 Feb 2006 08:12:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733824#M410</guid>
      <dc:creator>Joppe</dc:creator>
      <dc:date>2006-02-17T08:12:12Z</dc:date>
    </item>
    <item>
      <title>Re: rootsh and sudo problem</title>
      <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733825#M411</link>
      <description>Okay all I found a solution for my probblem that's working!&lt;BR /&gt;&lt;BR /&gt;I simply changed the default shell for the admin user to my rootsh, and added rootsh in the /etc/shells. And then I have logging from the first second a admin user loggs in to the server until he loggs out!&lt;BR /&gt;&lt;BR /&gt;Cheers &lt;BR /&gt;&lt;BR /&gt;Joppe&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 17 Feb 2006 08:29:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733825#M411</guid>
      <dc:creator>Joppe</dc:creator>
      <dc:date>2006-02-17T08:29:46Z</dc:date>
    </item>
    <item>
      <title>Re: rootsh and sudo problem</title>
      <link>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733826#M412</link>
      <description>Shalome Joppe,&lt;BR /&gt;&lt;BR /&gt;If sudo bash works you have no security at all and there is almost no reason to use sudo.&lt;BR /&gt;&lt;BR /&gt;The binaries that can be sudo must be limited by the sudoers file to make this setup effective.&lt;BR /&gt;&lt;BR /&gt;Leaving bash available for sudo is a huge back door that needs to be shut.&lt;BR /&gt;&lt;BR /&gt;As far a logging commands, you can set the HISTFILE variable and all commands input by keyboard logged. This can be in the home directores of your various admins or a central location.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 17 Feb 2006 14:41:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/secure-os-software-for-linux/rootsh-and-sudo-problem/m-p/3733826#M412</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-02-17T14:41:42Z</dc:date>
    </item>
  </channel>
</rss>

