mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Dean McEwan <dean_mcewan@linuxmail.org>,
	alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org
Subject: Re: Digital Rights Management - An idea (limited lease, renting, expiration, verification) NON HAR*D*WARE BASED.
Date: Wed, 14 May 2003 21:07:28 +0200	[thread overview]
Message-ID: <20030514190728.GA3478@louise.pinerecords.com> (raw)
In-Reply-To: <20030514161308.GA10374@parcelfarce.linux.theplanet.co.uk>

> [viro@parcelfarce.linux.theplanet.co.uk]
> 
> On Wed, May 14, 2003 at 03:22:46PM +0000, Dean McEwan wrote:
> > > That way around doesnt actually work because I'll simply lie, fake the server or firewall you
> > 
> > Encrypted binary, in a XML wrapper that needs decryption key from owners site.
> > Uses port 80...
> 
> ... and is declared a firing offense.  BTW, the privacy issues (and related
> information leak/blackmail potential) are mind-boggling - it's not just
> "some guy bought $material", it's "this guy had accessed $material at
> $list_of_times".
> 
> And that's besides being unable to use the FPOS in question on a laptop,
> going tits-up whenever a backhoe finds your cable, doing the same when
> vendor's boxen get screwed, yadda, yadda.
> 
> Crap idea.

Totally.

Two more problems:

1)  In this case the decryption key is an intergral part of the software
and as such needs to be supplied as per fair use clauses.

2)  Alan's argument stands.  It is possible to fake the server and provide
the key once the user have pinched a working copy.  The wrapper can be
reverse-engineered for communication key magics if need be.

-- 
Tomas Szepe <szepe@pinerecords.com>

  reply	other threads:[~2003-05-14 18:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 15:22 Dean McEwan
2003-05-14 16:13 ` viro
2003-05-14 19:07   ` Tomas Szepe [this message]
2003-05-15  6:46 ` Valdis.Kletnieks
2003-05-15 10:44 Dean McEwan
2003-05-15 11:17 ` Riley Williams
2003-05-19 11:01 ` Jakob Oestergaard
2003-05-15 14:19 Dean McEwan
2003-05-15 14:37 Dean McEwan

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=20030514190728.GA3478@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dean_mcewan@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@parcelfarce.linux.theplanet.co.uk \
    /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

Powered by JetHome