linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: Nick <nick@snowman.net>, Ricky Beam <jfbeam@bluetronic.net>
Cc: "Måns Rullgård" <mru@kth.se>, linux-kernel@vger.kernel.org
Subject: Re: Copy protection of the floppies
Date: Tue, 25 Nov 2003 22:55:39 -0500	[thread overview]
Message-ID: <200311252255.39823.gene.heskett@verizon.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0311251336250.24128-100000@ns.snowman.net>

On Tuesday 25 November 2003 13:37, 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

This "thread" has finally pulled my trigger, rant mode on.

Fugedaboutit.  The last piece of dongle protected software I tangled 
with was an A-B Roll video editor for the amiga.  The life of the 
parallel port dongle was about 9 months because they damaged the 
chips in it so badly in grinding off the identifications.

When the 3rd dongle died, and we found the outfit had been sold to 
somebody else, and it was discovered they didn't have any more 
dongles, and furthermore they weren't even sure we had rights to the 
fscking software!  We screwed around with them for about 6 months and 
I finally gave them the choice of seeing us in court or finding a 
dongle.  They got in the car and drove something like 400 miles one 
way to get the last dongle in existance off the authors home machine 
and sent it to us overnight.  They must have finally gotten the 
message that we were at the breaking point of being pissed and 
somebody was gonna bleed.

Frankly, we felt as if we had the right to make somebody bleed, color 
(red or green) optional since the software was part of a $25,000 
dollar video editing package (that wasn't the video tape recorders, 
just the software and networking hardware, we had another $50,000 in 
broadcast quality VCR's in that system) that we had paid around $2000 
just for updates of since we'ed bought it 2 years before this little 
rodeo started.

In the meantime we finally made good on our threat to send it out to 
the hackers (we told them that was one of our options and I think 
thats what got them to put the key in the switch and drive), and had 
a clean, no dongle required, version of it back in about 36 hours.  
And believe it or not, there is honor among the hackers who broke 
that for us, no copy was ever released into the wild.  And they did 
it just to prove they could, no charge folks!  Sometime later yet, 
they (RVS) wanted a copy of the one we had broken.  I left it to 
TPTB, but I think they were told to go pound sand just for being the 
ass-holes they had proved themselves to be.

Do you want to put your 'clients' thru that?  I think not if you want 
to sleep well at night.

We, as users, are normally pretty honest.  We screwed around with 
those jokers at RVS for 6 months before we did what we had to do, and 
I think that was 5 months and 23 days too long considering it was the 
production heart of a television station at the time.  That lack of a 
dongle for 6 months cost us about $125,000 in lost production 
revenues because our main editing suite was down.

It boils down to trusting your clients.  Most of us, if we need your 
software to do something that cannot be done any other way, will be 
glad to honor your rights to that software as long as it is actively 
supported even if its do almost nothing updates just to keep the cash 
cow coming fresh.  We fully understand that one needs a 'stream' of 
revenue for long term support.

OTOH, if the support goes away because you who originally asked the 
question no longer have a quarter to call somebody who cares, and its 
still the only thing that does that job, and your so-called 
protection methods get in the way, then you can fully expect that 
they will be rendered null and void.  Call it piracy, whatever, 
welcome to how the real world works. class 101.

Bottom line is treat us right, we'll treat you right.

End of rant...

[...]

-- 
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz  512M
99.27% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2003 by Maurice Eugene Heskett, all rights reserved.


  parent reply	other threads:[~2003-11-26  3:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  5:37 Copy protection of the floppies 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
2003-11-25 20:52         ` Ricky Beam
2003-11-26  3:55         ` Gene Heskett [this message]
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=200311252255.39823.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --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;
as well as URLs for NNTP newsgroup(s).