OK, I could accept that. Except that it's two months old. I can see
being a week, maybe two weeks (at the most) behind in security updates,
but not two months. Besides, keeping up on security issues and taking
appropriate action is part of the job. If a sysadmin isn't doing that,
then they aren't doing their job. A cursory glance at any security site
over the last two months is enough to know about the BIND issue. Also,
if said sysadmin puts a users LookOut problem before the overall well
being of their network, then they don't know how to prioritize.
Don't get me wrong, here. I'm not blaming it all on the poor sysadmin.
If a sysadmin really is that overworked that they cannot keep recent,
never mind current, on these issues, then management needs to wake up
and smell the exploit. But then again, management usually doesn't pay
attention until something happens and it's too late. I believe Bruce
Schneier said it best when he said " Anyone who believes that
reactionary security measures are sufficient is either ignorant, blind,
or management".
Kenny
Paul Lussier wrote:
>
> In a message dated: Fri, 23 Mar 2001 15:44:56 EST
> "Kenneth E. Lussier" said:
>
> >This worm just shouldn't be able to damage a site. If it does, then that
> >is an easy way to spot the sysadmins that aren't doing their jobs.
>
> Or, an easy way to spot and overworked, underpaid admin who doesn't
> have time to read security lists, become aware of these things, then
> take appropriate action.
>
> Don't blame it all on the poor slob to has all they can do just keep
> up with Windows virus problems and fixing someone's Outlook problems.
> --
>
> Seeya,
> Paul
> ----
> It may look like I'm just sitting here doing nothing,
> but I'm really actively waiting for all my problems to go away.
>
> If you're not having fun, you're not doing it right!
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
