From: "Bryan D. Stine" <admin@kentonet.net>
To: "Joseph D. Wagner" <wagnerjd@prodigy.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: GNU server "compromised"? Gimme a break!
Date: Thu, 14 Aug 2003 20:09:48 -0400 [thread overview]
Message-ID: <200308142009.53875.admin@kentonet.net> (raw)
In-Reply-To: <000601c362bf$7eadc9a0$62a14943@joe>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Err...have you ever used GRSec or SELinux? Both do (in-kernel btw) what you
claim does not exist in GNU/Linux. And SELinux is in 2.6... Do some research
next time.
On Thursday 14 August 2003 07:55 pm, Joseph D. Wagner wrote:
> I just think this goes a long way to say that GNU/Linux security sucks, the
> theory of a thousand eyes isn't true because the eyes aren't looking,
> GNU/Linux security sucks, FSF is administrated by incompetent boobs (notice
> that even their pre-hacked backups could be compromised -- um, "offsite
> backups" anyone?), GNU/Linux security sucks, auditing is non-existent
> because they can't tell who did what (they'd first need ACL's for this),
> GNU/Linux security sucks, backdoors can be in open source code, ... and did
> I mention that GNU/Linux security sucks?
>
> > -----Original Message-----
> > From: Scott McCollum [mailto:scott@worldtechtribune.com]
> > Sent: Thursday, August 14, 2003 5:14 PM
> > To: Joseph D. Wagner; bob@bobadkins.com
> > Subject: GNU server "compromised"? Gimme a break!
> >
> > http://www.internetnews.com/article.php/2248811
> >
> > So the excuse is that the GNU/Linux servers holding source code for the
> > Free Software Foundation was compromised will be how Stallman and his
> > cronies explain the fact that SCO-owned intellectual property got onto
> > their servers.
> >
> > How crazy does it sound when you say this out loud: "A hacker broke into
> > our open source servers and slipped proprietary code into the source code
> > of GNU/Linux in an attempt to plant evidence to frame us"?
> > -
>
> -
> 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/
- --
Bryan D. Stine
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/PCTQ4Cdq/Vbot6MRAtrtAJ4lFIA9Daxb/NeUW/4xJtT53f/4NACgiLVf
fhyqyKwYrU8CcCm5d4qre8A=
=rhKA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-08-15 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200308141813.AA266993698@worldtechtribune.com>
2003-08-14 23:55 ` GNU server "compromised"? Gimme a break! Joseph D. Wagner
2003-08-15 0:09 ` Bryan D. Stine [this message]
2003-08-15 0:26 ` Double-Harvard Architectures Akon
2003-08-15 1:23 ` Bernd Eckenfels
2003-08-15 6:58 GNU server "compromised"? Gimme a break! Bob Adkins
2003-08-15 7:34 ` David S. Miller
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=200308142009.53875.admin@kentonet.net \
--to=admin@kentonet.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wagnerjd@prodigy.net \
/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