[Committee-d] (no subject)

[Don Armstrong]

Unfortunatly, it looks like I'll be missing the 11th meeting too, as
I'll be in transit from LA.

drm_allowing_authentication basically needs another go round to see if
there are any significant problems.

Here's the current draft of the replacement for that clause for
starters:

Complete Corresponding Source Code also includes any encryption or
authorization codes necessary to install, compile (if required), and
execute the 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 the user has
specifically instructed the work to provide encrypted output, and can
instruct it to provide unencrypted output. Encryption or authorization
codes that the user can easily disable or replace with their own codes
and retain identical functioning need not be provided, so long as the
user can easily generate the codes or obtain them at no cost. A code
need not be included in cases where the use of the work normally
implies the user already has it.

http://svn.donarmstrong.com/don/trunk/projects/gplv3/issues/drm_allowing_authentication/
has the rest of things.


Don Armstrong

-- 
Cheop's Law: Nothing ever gets built on schedule or within budget.
 -- Robert Heinlein _Time Enough For Love_ p242

http://www.donarmstrong.com              http://rzlab.ucr.edu