|P is for Practical|
Generic Wrappers?by ninja_byte (Acolyte)
|on Dec 24, 2004 at 01:07 UTC||Need Help??|
ninja_byte has asked for the wisdom of the Perl Monks concerning the following question:
I'd like to develop 1 of 2 things(maybe just 1 big thing):
1. A Unix application wrapper
I handle a lot of abuse-related issues on a web hosting company server. Lots of abusers tend to use programs like lynx, wget, and curl to access malicious tools stored on their home computers or something. I'd like a wrapper to transparently snatch the argument list, log everything, investigate a bit, then pass the arguments to the actual program.
2. A Unix trapdoor application
Just a basic script that, when called/invoked,retrieves and logs as much information about the parent process as possible(OLDPWD, PPID, uid, blah blah). I'm open to ideas integrating non-perl programs within the application as well. This would be useful when I find someone actively using a malicious tool. I would replace their tool with this script, so they can call my replacement and voila... something.
OK so first off, are there any decent Modules that accomplish some or all of what I have in mind?
Can someone provide a bit of insight into the various info that I COULD gather from such a script(#2), or some rough pseudocode to structure such a script(#1).
I'm not new to sysadmin duties, only to perl itself. I look forward to this project, and all the rogue troublemakers that will surely be revealed....