<?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: Monitoring SSH sessions user activities in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334114#M34794</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Set the variables HISTFILE and HISTSIZE in the .profile for the user or /etc/profile and all commands will be recorded.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Thu, 08 Jan 2009 15:30:07 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2009-01-08T15:30:07Z</dc:date>
    <item>
      <title>Monitoring SSH sessions user activities</title>
      <link>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334113#M34793</link>
      <description>Hi All,&lt;BR /&gt;&lt;BR /&gt;We have a server, where all users connect to before connecting to other servers beyond it. &lt;BR /&gt;Is there a way/tool which monitor each user what is doing on these servers (what commands they are performing) and save these info in a file.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Jan 2009 15:07:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334113#M34793</guid>
      <dc:creator>M.S</dc:creator>
      <dc:date>2009-01-08T15:07:13Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring SSH sessions user activities</title>
      <link>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334114#M34794</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Set the variables HISTFILE and HISTSIZE in the .profile for the user or /etc/profile and all commands will be recorded.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 08 Jan 2009 15:30:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334114#M34794</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-01-08T15:30:07Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring SSH sessions user activities</title>
      <link>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334115#M34795</link>
      <description>The shell history indicated by SEP is user-modifiable, so it's no good if you need the logs for audit/legal purposes.&lt;BR /&gt;&lt;BR /&gt;We're using the "sudosh" utility to record any activities on system &amp;amp; application admin accounts on some critical systems, but the documentation indicates it's usable as a login shell wrapper too:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://en.wikipedia.org/wiki/Sudosh" target="_blank"&gt;http://en.wikipedia.org/wiki/Sudosh&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;It records everything the user sees and does.&lt;BR /&gt;It's available as a source package, so you'll have to compile it.&lt;BR /&gt; &lt;BR /&gt;Remember to allocate plenty of disk space for sudosh logs if you use it. If you run out of disk space for logs, your log record will of course be incomplete.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Thu, 08 Jan 2009 15:43:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334115#M34795</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-01-08T15:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring SSH sessions user activities</title>
      <link>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334116#M34796</link>
      <description>You could edit /etc/ssh/sshd_config and tell&lt;BR /&gt;sshd to wrap particular logins in a script command.  That is very intrusive.  There would be no privacy!&lt;BR /&gt;&lt;BR /&gt;# Log all output for users in group 'audited'&lt;BR /&gt;Match Group=audited&lt;BR /&gt;  ForceCommand script -qfa -c 'bash -i' /tmp/snoop_$USER&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The user needs access to the file that script is writing.  You can prevent them from overwriting that data if you direct script to write into a named pipe that the data is copied out of.&lt;BR /&gt;&lt;BR /&gt;# mknod /tmp/snoop_user1&lt;BR /&gt;# chmod 600 /tmp/snoop_user1&lt;BR /&gt;# cat &amp;lt; /tmp/snoop_user1 &amp;gt;&amp;gt; /var/log/snoop_user1 &amp;amp;&lt;BR /&gt;</description>
      <pubDate>Thu, 08 Jan 2009 16:45:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334116#M34796</guid>
      <dc:creator>Mike Stroyan</dc:creator>
      <dc:date>2009-01-08T16:45:49Z</dc:date>
    </item>
    <item>
      <title>Re: Monitoring SSH sessions user activities</title>
      <link>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334117#M34797</link>
      <description>Thx Guys,&lt;BR /&gt;&lt;BR /&gt;Sudosh was a good idea.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 09 Jan 2009 12:45:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/monitoring-ssh-sessions-user-activities/m-p/4334117#M34797</guid>
      <dc:creator>M.S</dc:creator>
      <dc:date>2009-01-09T12:45:01Z</dc:date>
    </item>
  </channel>
</rss>

