Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Thu, 18 Mar 1999 13:21:53 -0500 Message-Id: <199903181821.NAA28768@envy.delorie.com> From: DJ Delorie To: cgf@cygnus.com CC: creative1@bigfoot.com, cygwin@sourceware.cygnus.com In-reply-to: <19990318121728.B929@cygnus.com> (message from Chris Faylor on Thu, 18 Mar 1999 12:17:28 -0500) Subject: Re: licensing NOT clear for me References: <36F12160.87AE0FC0@bigfoot.com> <19990318111122.A792@cygnus.com> <36F12714.8EDF060A@bigfoot.com> <199903181635.LAA28111@envy.delorie.com> <19990318121728.B929@cygnus.com> > From the above, it seems to me that b) would be feasible for source > distributions on the web, unless "written offer" means something more > esoteric than actually including those words in a README. According to RMS, "written" means paper, with a date and signature (or other identifying mark). A computer file isn't legally binding because it can easily be modified. Personally, I would think a PGP-signed text file would be sufficient if it included the date inside the message, assuming you can verify the signature in the future (you can always generate a new PGP key and toss the old one). Still, you'd have to generate a new signed file every day (to get the full 3-year term) and the user can always download a new one to illegally extend their term. -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com