I'd like to package Mixmaster 2.9 (or 3.0, when it is released) for inclusion in Debian GNU/Linux, but there is a provision the license agreement that is incompatible with the Debian Free Software Guidelines. See <http://www.debian.org/social_contract#guidelines>. Unless a minor change is made to the license, I won't be able to package the software.
Of particular issue is item 1. B. (iii), which reads "provide Anonymizer Inc. with a copy of the Source Code of such modifications or work by electronic mail, and grant Anonymizer Inc. a perpetual, royalty-free license to use and distribute the modifications or work in its products." If Anonymizer, Inc. goes out of business or stops accepting email, then newly modified versions of Mixmaster become undistributable. Also, if the changes are frequent or substantial or the mail message must travel over a very slow or expensive connection, the requirement may represent an undue burden on the person making modifications. Immagine for a second the case of a political dissident in an oppressive nation who uses anonymous email to send quick snippets to news agencies in the rest of the world. He's discovered a security problem in Mixmaster and wants to share the fixed version with his buddies via sneakernet. He's using a bunch of extremely slow and expensive throwaway wireless and dialup links, and every time he keys up to transmit he risks revealing his location. As a result, he must keep transmissions very short and leave the area immediately afterwards. Why should he be forced to face either: 1. letting his friends use an insecure version of Mixmaster, or 2. emailing his substantial modifications to Anonymizer, Inc. and risking his location? If 1. B. (iii) was changed to read "grant Anonymizer Inc. a perpetual, royalty-free license to use and distribute the modifications under the terms of this license" it would meet our Free Software Guidelines, be safer for users that need anonymity the most, and would probably have the same overall effect for Anonymizer Inc. Would it be possible for this change to be made before the release of Mixmaster 3.0? -- Brian Ristuccia [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
