From: "Paul G. Allen" <pgallen@randomlogic.com>
To: "Linux kernel developer's mailing list" <linux-kernel@vger.kernel.org>
Subject: Re: SSSCA: We're in trouble now
Date: Wed, 06 Mar 2002 10:24:04 -0800 [thread overview]
Message-ID: <3C865EC4.8CD3A2A3@randomlogic.com> (raw)
In-Reply-To: <E16ieUY-0007MG-00@the-village.bc.nu>
Alan Cox wrote:
>
> > Just about every company big enough to have a corporate lawyer, and
> > many even smaller do have "media" they need or want to track and
> > control.
>
> One thing the SSSCA people must consider here is security impact. If a
> document can be traced through its users then the ability of agencies to
> work against organised crime will be crippled. The SSSCA appears to have no
> provision to allow the FBI to remove watermarks, and makes it illegalf or
> other people to be subcontracted to write the tools
>
> Goodbye corporate whistleblowers, goodbye FBI plants in organised crime
> bodies..
Oh, but the FBI and DoJ appear to be excellent at breaking laws and
making people, including the courts, believe they are completely within
the law. According to many reports, there are hundreds of people being
"detained" for undetermined amounts of time under the new anti-terroriam
bills, without legal counsel, by both the FBI and DoJ. This is blatantly
illegal and unconstitutional, but they are doing it anyway.
The DMCA makes it illegal for them to do certain things, but they do.
The way the NSA reportedly listens to ALL communication, domestic or
foreign, is illegal. Do not discount the ability of the FBI or any other
law enforcement agency to work around any law as they see the need.
PGA
--
Paul G. Allen
Owner, Sr. Engineer, Security Specialist
Random Logic/Dream Park
www.randomlogic.com
next prev parent reply other threads:[~2002-03-06 18:24 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
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 [this message]
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=3C865EC4.8CD3A2A3@randomlogic.com \
--to=pgallen@randomlogic.com \
--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