mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Nick <nick@snowman.net>
Cc: "Ricky Beam" <jfbeam@bluetronic.net>,
	"M�ns Rullg�rd" <mru@kth.se>,
	"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Copy protection of the floppies
Date: Tue, 25 Nov 2003 15:07:07 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.53.0311251501140.6546@chaos> (raw)
In-Reply-To: <Pine.LNX.4.21.0311251336250.24128-100000@ns.snowman.net>

On Tue, 25 Nov 2003, Nick wrote:

> Hardware dongles.  You need to be a bit creative but it can be done.  Say
> on save of the file output it to the hardware dongle with encrypts it with
> your private key, then on load of the file it gets decrypted with the
> public key, which is available, or some similar scheme.
> 	Nick
>

Dongles all use the same scheme! This means that if you've made
one program that uses a dongle, you can certainly emulate it!


> On Tue, 25 Nov 2003, Ricky Beam wrote:
>
> > On Tue, 25 Nov 2003, [iso-8859-1] Måns Rullgård wrote:
> > >> About 15 years ago, there were many gaming softwares which were procected,
> > (it was more than 15 years ago.)
> > >> for example, by checking "gap" between sectors.
> > >
> > >Can't that be done with a regular floppy drive and some special
> > >software?
> >
> > Please heed the lessons already learned in the software industry...
> > Copy protection doesn't work.  It works about as well as locks on doors
> > as it'll keep the honest people honest, and offer a small obstacle to
> > the dishonest.
> >

It'll keep honest people pissed and others entertained. In the
DOS days, there were holes burned into the floppies in certain
sectors. This kept diskcopy and other DOS stuff from copying
the floppies.  I just made a TSR that emulated the burnt holes
for the application and a copy routine that didn't care about
bad sectors (it ignored them).

The result was that you didn't need a "key" disk in drive A:
anymore. To the user, you just executed the program.

> > can do. (And given this thread, I can probablly do a few things you
> > currently cannot.)  Ultimately, any copy protection comes down to
> > the software on the floppy.  If the machine can read it to execute it,
> > the hacker can read it to remove the checks.  No ammount of hand-waving
> > will change that. (That, btw, is why the DMCA, et. al., exist.)
> >
> > --Ricky
> >

Cheers,
Dick Johnson
Penguin : Linux version 2.4.22 on an i686 machine (797.90 BogoMips).
            Note 96.31% of all statistics are fiction.



  reply	other threads:[~2003-11-25 20:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  5:37 Pravin Nanaware , Gurgaon
2003-11-25  9:07 ` Murray J. Root
2003-11-25  9:12 ` Måns Rullgård
2003-11-25  9:28 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-25  9:40   ` Måns Rullgård
2003-11-25 10:55     ` Matthias Andree
2003-11-25 16:07     ` Ricky Beam
2003-11-25 18:37       ` Nick
2003-11-25 20:07         ` Richard B. Johnson [this message]
2003-11-25 20:52         ` Ricky Beam
2003-11-26  3:55         ` Gene Heskett
2003-11-25 10:47 ` Helge Hafting
2003-11-25 20:18 ` Antonio Vargas
2003-11-25 20:32   ` Måns Rullgård
2003-11-26  3:58     ` Gene Heskett
2003-11-27  6:07 ` Willy Tarreau

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=Pine.LNX.4.53.0311251501140.6546@chaos \
    --to=root@chaos.analogic.com \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mru@kth.se \
    --cc=nick@snowman.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

all inboxes | Powered by JetHome®