SSL/Apache

[Ben Laurie <be...@gonzo.ben.algroup.co.uk>]

Yep, I've done it. It works. Sort of. Some problems with dropping connections
and the like, but basically, its there.

Now, does anyone have any serious suggestions as to how we deal with this?
I'm prepared to mail the patches to anyone that wants them (once they work a
bit better), and is in a country I think it is safe to mail to (i.e. UK and
Australia, currently). I don't think I'm currently prepared to take the risk of
sending them to the US. I am certainly not going to make them available on an
FTP site.

As to the copyright notice, I don't suppose (C) Apache Group is quite
appropriate? I'm happy enough to keep the license, tho.

Call me paranoid, or, more charitably, ultra-cautious   :-)

Cheers,

Ben.

-- 
Ben Laurie                  Phone: +44 (181) 994 6435
Freelance Consultant        Fax:   +44 (181) 994 6472
and Technical Director      Email: ben@algroup.co.uk
A.L. Digital Ltd,
London, England.

Re: SSL/Apache

["David J. Hughes" <ba...@Bond.edu.au>]

On Mon, 16 Oct 1995, Brian Behlendorf wrote:

> 1) mail the SSL-development mailing list.  I'm sure you'll find 
> compatriots who'll help you test it.  I wish I had the SSL-dev address 
> handy - anyone?

The best address would be  ssl-users@mincom.oz.au
There are people on this list (particularly Tim Hudson and Eric Young) 
who have vast experience with SSL'ifying (tm) applications.


Bambi
...

Re: SSL/Apache

[Brian Behlendorf <br...@organic.com>]

On Mon, 16 Oct 1995, Ben Laurie wrote:
> Now, does anyone have any serious suggestions as to how we deal with this?

1) mail the SSL-development mailing list.  I'm sure you'll find 
compatriots who'll help you test it.  I wish I had the SSL-dev address 
handy - anyone?

2) find a place to safely redistribute it.  Someone mentioned South 
Africa...

3) write an FAQ on how to use it - both what needs to be accomplished 
(license from RSA - or wait, was it Cylink now... ? - digital 
certificate from Verisign) and how to install it and test it with 
Netscape.  Look at the pages surrounding the support of SSL in NCSA's 
httpd (unofficial patches, etc) for some hints.


First though, which files did you need to patch?  I'm supposing it wasn't 
possible to implement as a module, but is there a way we could have 
extended the API to support it?  I'm thinking along the lines of making 
sure the patch can stay unchanged even if the core code of Apache changes 
dramatically...

You can put whatever copyright you want on it since it won't be 
distributed with the Apache source code.

	Brian


--=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=--
brian@organic.com  brian@hyperreal.com  http://www.[hyperreal,organic].com/