On the other hand, we try to keep the advertised (c) on binaries up to date.
About the only way to do that is to make updating the (c) date part of the build scripts, that's relatively easy on Windows as the resource file is text and gets compiled.
Which reminds me ... :{Peter
To be honest I'm not too sure what the policy here is, but I think we generally
don't update copyright messages unless some significant change is made. There
are a lot of files in the OpenSSL source code with these dates inI'd rather
not go through each one individually fixing them!
Matt
For what it's worth, the policy at IBM (where I used to work, and where they
know quite a few things about software intellectual property), is that you only
update the copyright on an individual file *when you modify it.*
/r$
--
Principal Security Engineer
Akamai Technologies,
I just clone the last release 1.0.1g and the file file ms\version32.rc still
mentions:
Copyright C 1998-2005 The OpenSSL Project. Copyright C 1995-1998 Eric A.
Young, Tim J. Hudson. All rights reserved.
shouldn't this sentence been updated ?
Arnaud
