From: Ben Ford <ben@kalifornia.com>
To: Gregory Maxwell <greg@linuxpower.cx>
Cc: "Richard B. Johnson" <root@chaos.analogic.com>,
Gerhard Mack <gmack@innerfire.net>,
Bob Lorenzini <hwm@newportharbornet.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux Worm (fwd)
Date: Mon, 26 Mar 2001 10:53:47 -0800 [thread overview]
Message-ID: <3ABF903B.1010906@kalifornia.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10103231028250.9403-100000@innerfire.net> <Pine.LNX.3.95.1010326095505.32103A-100000@chaos.analogic.com> <20010326102418.C18480@xi.linuxpower.cx>
What company was it that you worked for? I'm sure we could convince
them otherwise . . . .
-b
Gregory Maxwell wrote:
> On Mon, Mar 26, 2001 at 10:07:22AM -0500, Richard B. Johnson wrote:
> [snip]
>
>> I have just received notice that my machines will no longer be
>> provided access to "The Internet".
>>
>> "Effective on or before 16:00:00 local time, the only personal
>> computers that will be allowed Internet access are those administered
>> by a Microsoft Certified Network Administrator. This means that
>> no Unix or Linux machines will be provided access beyond the local
>> area network. If you require Internet access, the company will
>> provide a PC which runs a secure operating system such as Microsoft
>> Windows, or Windows/NT. Insecure operating systems like Linux must
>> be removed from company owned computers before the end of this week....."
>
>
> You've demonstrated over and over again that you work for a constantly
> stupid company.
>
> Please find someplace else to work, your issues have become more depressing
> then amusing. :)
>
> It's sad that people like the one who sent out messages like that can stay
> employed. In the last year there have been several Windows love-bug type
> worms each causing damaged estimated in the billions. One or two Linux worms
> that go after a long fixed problem with no published accounts of significant
> damage and you get that sort of email..
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-03-26 18:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 17:49 Linux Worm (fwd) Bob Lorenzini
2001-03-23 18:30 ` [OT] " Jonathan Morton
2001-03-23 18:31 ` Gerhard Mack
2001-03-23 18:51 ` [OT] " Doug McNaught
2001-03-23 19:39 ` Michael Bacarella
2001-03-23 22:19 ` Herbert Xu
2001-03-24 0:39 ` Edward S. Marshall
2001-03-24 17:11 ` Jesse Pollard
2001-03-24 17:50 ` Edward S. Marshall
2001-03-24 19:02 ` Sandy Harris
2001-03-23 18:56 ` Dax Kelson
2001-03-23 19:08 ` Jeremy Jackson
2001-03-23 20:30 ` Michael H. Warfield
2001-03-26 15:07 ` Richard B. Johnson
2001-03-26 15:24 ` Gregory Maxwell
2001-03-26 16:02 ` Bob_Tracy
2001-03-26 16:11 ` offtopic " John Jasen
2001-03-27 1:14 ` Drew Bertola
2001-03-26 18:53 ` Ben Ford [this message]
2001-03-26 15:40 ` David Weinehall
2001-03-26 16:51 ` Bob Lorenzini
2001-03-26 16:51 ` Henning P. Schmiedehausen
2001-03-26 18:32 ` Stephen Satchell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ABF903B.1010906@kalifornia.com \
--to=ben@kalifornia.com \
--cc=gmack@innerfire.net \
--cc=greg@linuxpower.cx \
--cc=hwm@newportharbornet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox