From owner-freebsd-questions Mon Feb 7 9:30:22 2000 Delivered-To: freebsd-questions@freebsd.org Received: from almazs.pacex.net (almazs.pacex.net [204.1.219.156]) by builder.freebsd.org (Postfix) with ESMTP id E7E93401C for ; Mon, 7 Feb 2000 09:30:18 -0800 (PST) Received: from localhost (danielb@localhost) by almazs.pacex.net (8.9.3/8.9.3) with ESMTP id JAA79464 for ; Mon, 7 Feb 2000 09:27:26 -0800 (PST) Date: Mon, 7 Feb 2000 09:27:26 -0800 (PST) From: daniel B To: freebsd-questions@freebsd.org Subject: Apache SSL and licensing/US crypto rules Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good monday morning all; We are trying to implement SSL on our commercial Apache web server which runs on FreeBSD. I have done some extensive reading(looking for ways I can do this with open source stuff and careful about US crypto rules). I can't run Apache with OpenSSL (mod_ssl) which is freely and legally available EXCEPT IN THE US! I can't use RSAref implementation for SSL purpose without paying licensing fee it is a patented technology in the US and SSLeay uses RSA methods I simply want to add the SSL feature to our servers; customers can pay for certificates of authorities... seperately if they need them, I just need standard 40 byte encryption for some of the stuff that runs on our web servers, and if I have to pay I would rather donate the money to open source where it will be used for the good of all!! help please Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message