From: jim <jim.whitson@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] www.sco.com
Date: Mon, 29 Nov 2004 14:54:50 +0000 [thread overview]
Message-ID: <9EC68386-4216-11D9-985D-00112430C042@gmail.com> (raw)
In-Reply-To: <41AB369A.90703@9fs.org>
On 29 Nov 2004, at 14:47, Nigel Roles wrote:
> fgergo@gmail.com wrote:
>
>> If you take a look quickly www.sco.com, you might still get a glimpse
>> on a (hopefully) hacked sco main page.
>>
>> gergo
>>
>> ps: If you don't see anything I'll put up a screenshot to some public
>> place later today.
>>
>>
> I don't think that'll be necessary. It's getting more press coverage
> than
> David Blunkett's love life.
>
lol.
> See
>
> http://www.theregister.co.uk/2004/11/29/sco_hacked/
>
The site was also defaced last night, by the same attacker:
http://www.zone-h.org/defaced/2004/11/29/www.sco.com/redhat/ .
cheers,
jim
prev parent reply other threads:[~2004-11-29 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 14:08 fgergo
2004-11-29 14:47 ` Nigel Roles
2004-11-29 14:54 ` jim [this message]
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=9EC68386-4216-11D9-985D-00112430C042@gmail.com \
--to=jim.whitson@gmail.com \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).