[Committee-d] DRM and Allowing Authentication Draft

[Don Armstrong]

Here is the current draft of the changes to section 1 that I'm going
to suggest to deal with this particular issuee. It's still rather
suboptimal, but I think I'm moving in the proper direction.

Suggestions about the current draft appreciated.

Original:

Complete Corresponding Source Code also includes any encryption or
authorization codes necessary to install and/or execute the source
code of the work, perhaps modified by you, in the recommended or
principal context of use, such that its functioning in all
circumstances is identical to that of the work, except as altered by
your modifications. It also includes any decryption codes necessary to
access or unseal the work's output. Notwithstanding this, a code need
not be included in cases where use of the work normally implies the
user already has it.

Modification:

Complete Corresponding Source Code also includes any encryption or
authorization codes necessary to install, compile (if required), and
execute the covered work, perhaps modified by you, such that its
functioning in all circumstances is identical to that of the work,
except as altered by your modifications. It also includes any
decryption codes necessary to access or unseal the work's output
unless you have specifically instructed the work to provide encrypted
output, and can instruct it to provide unencrypted output. Encryption
or authorization codes that you can disable or replace with your own
codes and retain identical functioning need not be provided, so long
as you can generate the codes or obtain them at no cost to you. A code
need not be included in cases where the use of the covered work
normally implies you already have it.


Wdiff Output:

Complete Corresponding Source Code also includes any encryption or
authorization codes necessary to [-install and/or-] {+install, compile
(if required), and+} execute the [-source code of the-] {+covered+}
work, perhaps modified by you, [-in the recommended or principal
context of use,-] such that its functioning in all circumstances is
identical to that of the work, except as altered by your
modifications. It also includes any decryption codes necessary to
access or unseal the work's {+output unless you have specifically
instructed the work to provide encrypted output, and can instruct it
to provide unencrypted+} output. [-Notwithstanding this, a-]
{+Encryption or authorization codes that you can disable or replace
with your own codes and retain identical functioning need not be
provided, so long as you can generate the codes or obtain them at no
cost to you. A+} code need not be included in cases where {+the+} use
of the {+covered+} work normally implies [-the user-] {+you+} already
[-has-] {+have+} it.


As always the most current version is available at
http://svn.donarmstrong.com/don/trunk/projects/gplv3/issues/drm_allowing_authentication

I'll try to remember to stick a pdf in an accessible location, or you
can build the pdf yourself if you want. [You'll just need rubber,
latex and wdiff.]


Don Armstrong

-- 
The attackers hadn't simply robbed the bank. They had carried off
everything portable, including the security cameras, the carpets, the
chairs, and the light and plumbing fixtures. The conspirators had
deliberately punished the bank, for reasons best known to themselves,
or to their unknown controllers. They had superglued doors and
shattered windows, severed power and communications cables, poured
stinking toxins into the wallspaces, and concreted all of the sinks
and drains. In eight minutes, sixty people had ruined the building so
thouroughly that it had to be condemed and later demolished.
 -- Bruce Sterling, _Distraction_ p4

http://www.donarmstrong.com              http://rzlab.ucr.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://gplv3.fsf.org/pipermail/committee-d/attachments/20060312/ebe191b7/attachment.pgp