public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "Linux kernel developer's mailing list"  <linux-kernel@vger.kernel.org>
Cc: "kplug-list@kernel-panic.org" <kplug-list@kernel-panic.org>,
	"kplug-lpsg@kernel-panic.org" <kplug-lpsg@kernel-panic.org>,
	newbie <kplug-newbie@kernel-panic.org>
Subject: Re: SSSCA: We're in trouble now
Date: Mon, 04 Mar 2002 09:02:52 -0800	[thread overview]
Message-ID: <3C83A8BC.B1CC16B2@randomlogic.com> (raw)
In-Reply-To: <1015028463.2276.231.camel@thanatos> <87bse7nz8g.fsf@CERT.Uni-Stuttgart.DE> <20020304083055.GB21138@hh.idb.hist.no> <003d01c1c360$96194600$0201a8c0@homer>

[Cross posted for informational importance]

Martin Eriksson wrote:
> 
> 
> My stepfather just recently figured out that you can actually DRAG a window
> around the desktop. I don't think he will be using a rootkit in some time,
> and I am pretty sure he don't know anyting about SSSCA, nor will he, nor
> will he be able to understand if I told him.
> 

You've touched on one of the main problems that spurs these kinds of
laws along through the system: People don't know about them or
understand them. Those of us that do know and understand them, and their
implications, need to speak up and explain them to those that do not.
Not doing so just gives those trying to push them through (and
succeeding) more power to do so. Those that draft, support, lobby, and
push for these kinds of laws often count on the fact that the public in
general is naive and are not paying enough attention to know what is
good and what is not good for them, or to even have a clue as to what is
going on on Capital Hill (or in Parliament, or wherever). They also rely
upon the Fear Factor.

The resent Anti Terrorism bills passed here in the U.S. were just
waiting for something to allow them to pass easily. Many of the policies
in these laws were drafted long before 9/11, and attempts were made to
make them law long before 9/11. Those attempts failed because either
people were aware of them each for what they were, or the law drafters
were not comfortable that they would pass. Along comes 9/11, and
suddenly people are more afraid of what would happen to them without a
new law (the Fear Factor), than what might happen with a new law. They
also did not pay much attention to the actual contents of the law
(herein lies the "not understanding, naive, not paying attention" part)
and allowed many concessions to to their freedom be made on the premise
of the government protecting them against terrorism. There are already
plenty of laws that would mandate a terrorist be prosecuted (or a
non-terrorist committing many of the crimes that were thrown into the
recent anti-terrorism laws), but it seems the powers that be just wanted
more control.

The bottom line is, to many too often sit and do nothing until they come
to realize it's too late to do anything other than the drastic. Is this
to be the trend when it comes to Open Source, including Linux? Maybe the
SSSCA or other laws will have no effect, but then maybe they will. I for
one do not wish to sit on my rear and wait to find out it (or they)
have.

PGA
-- 
Paul G. Allen
Owner, Sr. Engineer, Security Specialist
Random Logic/Dream Park
www.randomlogic.com

  reply	other threads:[~2002-03-04 17:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-02  0:21 SSSCA: We're in trouble now Thomas Hood
2002-03-02  8:35 ` Florian Weimer
2002-03-02 17:34   ` M. Edward (Ed) Borasky
2002-03-04  8:30   ` Helge Hafting
2002-03-04  9:40     ` Martin Eriksson
2002-03-04 17:02       ` Paul G. Allen [this message]
2002-03-06  4:41     ` Petro
2002-03-06  9:27       ` Helge Hafting
2002-03-02 15:30 ` Paul P Komkoff Jr
2002-03-02 21:58   ` Rik van Riel
2002-03-03  1:29     ` Greg Louis
2002-03-06  4:51   ` Petro
2002-03-02 17:47 ` Jurgen Botz
2002-03-06  5:00   ` Petro
2002-03-06 16:42     ` Alan Cox
2002-03-06 18:24       ` Paul G. Allen
2002-03-06 23:56       ` Petro
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06 17:20 Ed Vance
2002-03-06 18:31 ` Paul G. Allen
2002-03-04 19:27 Jesse Pollard
2002-03-01 19:46 Paul G. Allen
2002-03-01 20:27 ` Shawn Starr
2002-03-01 20:30   ` Xavier Bestel
2002-03-01 21:29     ` Shawn Starr
2002-03-01 22:19       ` Alan Cox
2002-03-02  3:08         ` Neale Banks
2002-03-02  3:03           ` eddantes
2002-03-02 18:32           ` Alan Cox
2002-03-01 22:47       ` Florian Weimer
2002-03-02  2:59         ` Paul G. Allen
2002-03-06  4:26           ` Petro
2002-03-06  4:41             ` Trever L. Adams
2002-03-06 16:26               ` Rik van Riel
2002-03-06 17:03                 ` Richard B. Johnson
2002-03-06 18:16                 ` Paul G. Allen
2002-03-06 18:35                 ` Trever L. Adams
2002-03-07 22:54                 ` Florian Weimer
2002-03-08  2:12                   ` Tom Rauschenbach

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=3C83A8BC.B1CC16B2@randomlogic.com \
    --to=pgallen@randomlogic.com \
    --cc=kplug-list@kernel-panic.org \
    --cc=kplug-lpsg@kernel-panic.org \
    --cc=kplug-newbie@kernel-panic.org \
    --cc=linux-kernel@vger.kernel.org \
    /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