Chris Pomerantz wrote:
> 
> As far as I know, and that's only what I've read on the web, is when you
> purchased your Re Hat software it should have come with the license to use
> the encryption. This is because Red Hat bought a license to be able to
> resell you the software, in turn giving you a legal right to use encryption
> technology. This what I have read else where, it may have even been on the
> OpenSSL site somewhere, but don't quote me on that.

It is correct. Red Had purchased from RSA a license that allows them to sell
their encryption technology in their software package. (These licenses go for
$25k+.)

What you can do:
Use mod_ssl that comes with Red Hat Secure Web Server.

What you can *not* do:
Update it with a newer version by recompiling it yourself. However, updates are
occasionally made available by Red Hat.



> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of keiths
> Sent: Friday, June 23, 2000 1:23 PM
> To: [EMAIL PROTECTED]
> Subject: A little legal help, please...
> 
> I have just spent a day adding in support for SSL via mod-ssl to my
> apache server.  I am new to all this stuff and have just been told -
> "make it secure" - and it seemed to me this is the logical way to go.
> We purchased a Red Hat Linux Pro software, including the "Secure Web
> Server", and when I initially installed it a few months ago I had
> problems with it and jserv.  Security was not an issue at that time, so
> I picked up fresh 3.1.9 apache source, and fresh jserv source which
> worked pretty much without a hitch.
> 
> Now I apply the same approach to doing a DSO for SSL, and get it going
> and then discover that there are legal issues.  Browsing through some of
> your archives, it seems that it might be reasonable to use the license
> for the outofthebox red hat SWS for the mod-ssl.  Have I gotten the
> wrong message, or will I have to go back to the outofthebox stuff.
> 
> Many thanks in advance, and hope that I can become a "real" subscriber
> soon, if not after Sept 20th.

S/MIME Cryptographic Signature

Reply via email to