I wrote:
> 1. Add a statement to the top of the file LICENSE.OpenSSL saying that
> since it was effectively an extension to the license statements in the
> individual source files in the hpoj package, only the copyright holder(s)
> of those source files (namely HP) may update the LICENSE.OpenSSL fi
Richard Stallman wrote:
> I see one possible flaw: if someone includes a different COPYING.OpenSSL
> file, this notice would give permission for linking with something
> under that replaced file. I think that's a bug. It needs to state
> the OpenSSL license in some more reliable way.
Hi, Richard
I have checked into CVS the license changes which explicitly allow
linking with OpenSSL. If anybody would like to inspect these changes,
here are some sample files:
http://hpoj.sourceforge.net/hpoj-cvs/LICENSE
http://hpoj.sourceforge.net/hpoj-cvs/LICENSE.OpenSSL
http://hpoj.sourceforge.net/hpoj-c
Hi, Andreas. Thanks for your quick response, and I apologize again for
phoning you at work. :-) Thanks for your comments about the progress
of the project, and I'm sure you'll find the next version (0.90) to be
even better, especially in the area of scanning support. Thanks also
to Roger, Gerha
Jeff Licquia wrote:
> My gut reaction is to trust that you (David) are a reasonable person,
> seeing as how you've been forthright so far, and will intentionally
> refuse to take advantage of our situation. Should you suddenly
> metamorphize into an ogre, however, we do have the legal recourse of
5 matches
Mail list logo
