If you are going to go to that much trouble, why not make it really official
and register with the US Copyright Office.

http://www.loc.gov/copyright/reg.html
Look for circular 61.

It costs $20.00 to register your program ($30.00 after 6/30/99).  There is a
"Short Form TX" (only seven data elements to complete) to fill out.  You
send in a printout of part of your source code.  If your source code
contains trade secrets your are allowed to block them out. That's really
pretty much it. I was surprised how simple it is.  You don't need a lawyer.



> -----Original Message-----
> From: Tom Zerucha [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, June 11, 1999 12:33 AM
> To:   [EMAIL PROTECTED]
> Subject:      re:copyrights (was: Re: cracking site - how do we shut it
> down?)
> 
> On Thu, 10 Jun 1999, Matthew D Moss wrote:
> 
> > >as far as US copyright law is defined, this is correct.  works are
> > >considered copyrighted (?) as soon as they are presented to others.
> > >just mark it with the copyright lingo mentioned below.  the only reason
> > >for registering your copyrights is to be able to prove in court who had
> > >it first.  that is considered the only real, legal proof.
> > 
> > One scheme I recall hearing to use as proof of date is the following.
> Take
> > the copyrighted work, place it in an envelope, seal it, and mail it to
> > yourself.  When you receive it back, DO NOT OPEN IT.  The cancellation
> on
> > the stamp contains the date and year.
> 
> This would be limited proof, but I think it would be better to have it
> notarized (which includes a witness).  I think most Kinkos copier places
> have this service for a very small fee.
> 
> > I don't know if would hold up in a court, but it seems reasonable
> precaution
> > if it matters that much to you.  I would also guess you could mail
> yourself
> > a floppy disk containing source code (rather than reams of printouts).
> 
> Or optionally encrypt it, and use a PGP timestamping service.  One was at
> http://www.itconsult.co.uk/stamper.htm
> last time I checked.
> 

Reply via email to