linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bob Adkins" <bob@bobadkins.com>
To: <scott@worldtechtribune.com>, "Joseph D. Wagner" <wagnerjd@prodigy.net>
Cc: "Bob Adkins" <bob@bobadkins.com>,
	"Linux GCC" <linux-gcc@vger.kernel.org>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: RE: GNU server "compromised"? Gimme a break!
Date: Fri, 15 Aug 2003 02:58:07 -0400	[thread overview]
Message-ID: <200308150258.AA331677844@bobadkins.com> (raw)

But, it is free!  

I have heard this story before.  Sharing is good.  Freedom, Openess, New World, ...

This is the same foo foo juice that created a generation of single mothers and millions of teens with sexually communicated disease.  The same drunkenness that made it ok to kill millions of babies.  The same BS that created millions of drug users, teen drunks, and theives.  The same spirit that has wiped out millions of kids and just robbed them of any future at all.

They were all defiant.  Anti-establishment.  Claming that, "it is MY body and no one else has the right..."

The end results were really bad and will cause generations of pain.

Stallman and Company are just a bunch of stalled out juvenile delinquents that never grew up.  

Peter Pan from the Dark Side.  The merging of the evil of two consecutive generations into a force for change.  That was called Bolshevism at the turn of the last century.  This century, it is called Open Source.  Both were singing the same songs and making the same speeches and marching with the same crowd.  

Both are likely to meet similar ends.  I hope the end of Open Shit is a little less bloody.  The Leninists killed all the Bolsheviks as soon as they had outlived their usefulness.  

Liberated.  Free.  Open.  Common.  Yeah, right!  Dead and dying is a simpler, and more accurate description.





---------- Original Message ----------------------------------
From: "Joseph D. Wagner" <wagnerjd@prodigy.net>
Date:  Thu, 14 Aug 2003 18:55:05 -0500

>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"?
>> -
>
>-
>
>
-


             reply	other threads:[~2003-08-15  6:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15  6:58 Bob Adkins [this message]
2003-08-15  7:34 ` GNU server "compromised"? Gimme a break! David S. Miller
     [not found] <200308141813.AA266993698@worldtechtribune.com>
2003-08-14 23:55 ` Joseph D. Wagner
2003-08-15  0:09   ` Bryan D. Stine

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=200308150258.AA331677844@bobadkins.com \
    --to=bob@bobadkins.com \
    --cc=linux-gcc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott@worldtechtribune.com \
    --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;
as well as URLs for NNTP newsgroup(s).