From: Thomas Dodd <ted@cypress.com>
To: linux-kernel@vger.kernel.org
Cc: Andre Hedrick <andre@linux-ide.org>
Subject: Re: new generic content schemes popping up everywhere...
Date: Tue, 13 Mar 2001 13:39:55 -0600 [thread overview]
Message-ID: <3AAE778B.8418D1E9@cypress.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10103131000410.2900-100000@master.linux-ide.org>
Andre Hedrick wrote:
> >From siliconvalley.com's GMSV column today:
> self-destruct if it's tampered with. The utility is enabled
> with 11 layers of security defenses, all of which must be
> successfully navigated to disable the system. These layers
> range from a series of forced reboots designed to thwart
> automated hacking tools to something called "the white screen
> of death" which destroys the software and all files stored
> inside it. Infraworks CEO George Friedman says the
> application's system-level control is possible largely because
> it is firmly anchored into users' C drives during
> installation. "We're fairly deep in the operating system,"
Not much help if you put the disk in another box without their
system installed (or mount in linux/BSD/MacOS) to break the
encryption/controls. Once that's done, A floppy based OS
and tool could break open the files on a disk, when their
apps aren't running.
If it can be decrypted "legally" it can
be done "illegally" too.
-Thomas
next prev parent reply other threads:[~2001-03-13 21:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 18:02 new generic content schemes popping up everywhere Andre Hedrick
2001-03-13 19:39 ` Thomas Dodd [this message]
2001-03-13 22:00 ` James A. Sutherland
2001-03-13 22:59 ` Jonathan Morton
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=3AAE778B.8418D1E9@cypress.com \
--to=ted@cypress.com \
--cc=andre@linux-ide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.