comment on

I'm not actually using it now, I'm considering a small private project to explore Log4Perl.

As far as work situations are concerned, what I meant by security info isn't very different from Apache logging, it's just a matter of context.

In particular, at the bank where I worked last winter (hi Vlad), they had a special account WXYZ which ran certain programs, and people would log on as WXYZ and run scripts. Well, that's not very different from logging on as root. So we came up with an suid script named wxyz which would let outside people run programs uzing the WXYZ account ... a first step in migrating away from SU anonymity.

Previously, you knew that fifty people had logged on as WXYZ and one of them had run 'rm -rf *'. With the new system, you knew who had done what, because the system logged the requests.

--
TTTATCGGTCGTTATATAGATGTTTGCA

In reply to Re: Re: Re: Serious & personal meditation by TomDLux
in thread Serious & personal meditation by perlinux

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


good chemistry is complicated, and a little bit messy -LW
	PerlMonks