From: "Dean McEwan" <dean_mcewan@linuxmail.org>
To: core@enodev.com
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Digital Rights Management - An idea
Date: Wed, 14 May 2003 15:40:28 +0000 [thread overview]
Message-ID: <20030514154028.12556.qmail@linuxmail.org> (raw)
> 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...
> Anyway, assuming you meant "downloaded file == any file", that's simple,
> and already being discussed, most likely by companies like TiVo, etc.
>
FOR LINUX?
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
next reply other threads:[~2003-05-14 15:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 15:40 Dean McEwan [this message]
2003-05-14 16:46 ` Digital Rights Management - An idea Shawn
2003-05-15 9:25 ` Paul Rolland
-- 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=20030514154028.12556.qmail@linuxmail.org \
--to=dean_mcewan@linuxmail.org \
--cc=core@enodev.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.