Date: Thu, 6 Dec 2012 20:10:23 +0000 From: Steve O'Hara-Smith <ateve@sohara.org> To: freebsd-questions@freebsd.org Cc: tundra@tundraware.com Subject: Re: Somewhat OT: Is Full Command Logging Possible? Message-ID: <20121206201023.750cace0181d4756a3111c2f@sohara.org> In-Reply-To: <50C0EFA4.3010902@tundraware.com> References: <50BFD674.8000305@tundraware.com> <8BFA2629-45CA-491B-9BA8-E8AC78A4D66E@my.gd> <50BFDCFD.4010108@tundraware.com> <CALf6cgb0%2BGXrtTymOPOmjV_C2sk7EaGK=qJOF2z4mB3pQkzV_g@mail.gmail.com> <50C0EFA4.3010902@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 06 Dec 2012 13:19:00 -0600 Tim Daneliuk <tundra@tundraware.com> wrote: > On 12/06/2012 12:55 PM, n j wrote: > > On Thu, Dec 6, 2012 at 12:47 AM, Tim Daneliuk <tundra@tundraware.com> > > wrote: > >> ... > >> Well ... does auditd provide a record of every command issued within a > >> script? > >> I was under the impression (and I may well be wrong) that it noted > >> only the name of the script being executed. > > > > Even if you configured auditd to record every command issued within a > > script, you'd still have a problem if a malicious user put the same > > commands inside a binary. > > > > As some people already pointed out, there is practically no way to > > control users once you give them root privileges. > > I understand this. Even the organization in question understands > this. They are not trying to *prevent* any kind of access. All > they're trying to do *log* it. Why? To meet some obscure > compliance requirement they have to adhere to in order to > remain in business. It occurs to me to wonder how the users are connecting to the machine and whether the logging could be achieved at that level using (for example) a customised sshd that logs all the traffic. It doesn't quite log what commands get executed but it does log what gets typed and everything else will follow from that. -- Steve O'Hara-Smith <ateve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121206201023.750cace0181d4756a3111c2f>