On Thu, Dec 9, 2010 at 11:29, unix_fan <[email protected]> wrote:
> Yes, I am going to stir this particular pot.
>
Looks tasty!
> "Privacy
> I will access private information on computer systems only when it is
> necessary in the course of my technical duties.
>
>From an operational standpoint, this probably isn't relevant to the sysadmin
(unless it's discovered that a sysadmin was the one responsible for the
initial leak). Once it's published, it's published, and at that point the
sysadmin's job is just to keep the Web site hosting the information
up-and-running, or to ensure the end-users can reach that Web site.
1. Be doing their best to defend their employer's sites against a DDOS
>
Which we'd have to do anyway, because a DDOS could come at just about any
time. Someone might get upset that I'm hosting a small jewelry store's Web
site because they have a gold allergy, or something equally silly.
2. Not engage in a DDOS against another site
>
Again, you'd probably be doing this regardless, as part of things like
"keeping your users' computers free from viruses and such."
There's an interesting edge case in the LOIC ("Low Orbit Ion Cannon,"
software that someone on 4chan whipped up that lets you voluntarily
participate in DDOS attacks), though. Let's say you're the network guy for a
residential ISP. If one of your users freely installs this software, how do
you respond?
David Smith
MVN.net
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
