[Prev][Next][Index][Thread]

Re: Perl Co-inventor Convicted



>Once again: you're displaying the attitude that a boss is NECESSARILY male.
>And this is the kind of mindset that can get you into very big trouble.  [I
>do wish the Spivak set of gender-neutral pronouns would catch on (check out
>_The Joy of LaTeX_ for an introduction to Spivak, which is also used on
MOOs
>round the world).]

Hey, I use grammatically correct English, and since I am and have been a
boss
myself, I figure I'm entitled to use "he" generically without being accused
of sexism. ;-)

>More seriously, though, I have to agree that getting approval for this sort
>of thing only makes sense.  However, I think Intel's setting a very
>dangerous precedent here.  I don't mean a legal precedent, either; it fails
>to surprise me that the courts can't tell the difference between security
>administration and cracking.

According to the police reports, which were reposted recently, Schwartz
admitted to the detective that he knew that was he was doing was technically
illegal, that he had been confronted by coworkers more than once and asked
to stop what he was doing (and yet he continued), and that his motivation
for cracking the systems was to create back doors for himself so that he
could retain access after his contract for those machines expired.  I don't
know about you, but based on that testimony, I think the courts called it
pretty well.

>But Intel has set a very dangerous management precedent.  I, for one, might
>now be far more likely to decide a hypothetical employer's security
>situation can be as lousy as it wants to be, rather than going through
>ridiculous beaurocratic hoops to get permission to try and find out what
>needs to be cleaned up.

Don't be silly.  Just ask before you do it.  Really, how hard is that to
do??
NOBODY in this entire discussion has presented a good argument against
ASKING FIRST.  I hardly think that having an open dialogue with your
immediate supervisor constitutes a "bureaucratic hoop."





----

Wendy Nather
wendy@swissbank.com


Follow-Ups: References: