From: "Paul Rolland" <rol@as2917.net>
To: "'Dean McEwan'" <dean_mcewan@linuxmail.org>, <core@enodev.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Digital Rights Management - An idea
Date: Thu, 15 May 2003 11:25:59 +0200 [thread overview]
Message-ID: <011201c31ac3$ffa7d580$3f00a8c0@witbe> (raw)
In-Reply-To: <20030514154028.12556.qmail@linuxmail.org>
> > How exactly would you do this specifically for "downloaded" files
> > except by snooping into every ftp/http, much less having to decrypt
> > the protocols like https or scp?
>
> Files would be recompiled for DRM...
>
Which would make it impossible to import even the simplest text data
file on such a machine ????
Paul
next prev parent reply other threads:[~2003-05-15 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 15:40 Digital Rights Management - An idea Dean McEwan
2003-05-14 16:46 ` Shawn
2003-05-15 9:25 ` Paul Rolland [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 10:46 Dean McEwan
2003-05-14 8:30 Dean McEwan
2003-05-14 8:39 ` Paul Rolland
2003-05-14 10:50 ` Alan Cox
2003-05-14 14:27 ` Shawn
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='011201c31ac3$ffa7d580$3f00a8c0@witbe' \
--to=rol@as2917.net \
--cc=core@enodev.com \
--cc=dean_mcewan@linuxmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox