public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Dean McEwan" <dean_mcewan@linuxmail.org>
To: alan@lxorguk.ukuu.org.uk
Cc: 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 15:22:46 +0000	[thread overview]
Message-ID: <20030514152247.4146.qmail@linuxmail.org> (raw)


----- Original Message -----
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Date: 14 May 2003 14:49:03 +0100 
To: Dean McEwan <dean_mcewan@linuxmail.org>
Subject: Re: Digital Rights Management - An idea (limited lease, renting, expiration, verification) NON HARWARE BASED.

> On Mer, 2003-05-14 at 14:52, Dean McEwan wrote:
> > It would be set up so that files have an internal signature (ELF format might have to be
> > fiddled with). It would verify itself by sending info to the creator of the contents PC OR server
> > asking for verification of itself, files could be limited lease, rented, or automatically expire 
> > after some time.
> 
> 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...
> (in fact any serious business firewalls all outgoing traffic from end users). If you want
> to do it for internal trust and you control the systems (the useful case) you set SELinux
> or RSBAC up so that all applications create files in a "non runnable" class. The only way
> to transition an app is a single user application which does your key checking and other
> processing then transitions the binary to "safe". I guess you also add a general rule that
> writing to a file moves it back into non runnable.
> 
> One of the problems with this is interpreters. Its easy to do this with ELF binaries but
> you have to extend it to scripts and that normally means more pain 8)
> 
> 
> 

-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

             reply	other threads:[~2003-05-14 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 15:22 Dean McEwan [this message]
2003-05-14 16:13 ` Digital Rights Management - An idea (limited lease, renting, expiration, verification) NON HAR*D*WARE BASED viro
2003-05-14 19:07   ` Tomas Szepe
2003-05-15  6:46 ` Valdis.Kletnieks
  -- strict thread matches above, loose matches on Subject: below --
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=20030514152247.4146.qmail@linuxmail.org \
    --to=dean_mcewan@linuxmail.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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