[Zope3-dev] Certification: Twisted versus Zope / native HTTPS or Apache

[Christian Theune]

Hi,

Am Mittwoch, den 14.12.2005, 13:03 +0100 schrieb Christian Theune:
> Ok. So in favor of the mainstream (and trusted!) configuration, I'll go
> for using the standard Twisted/HTTP server in combination with a local
> Apache that provides SSL to the web browser.

Actually that also means that I only will mention Apache as an
additional add-on, because we do not want to certify the Apache setup
itself. It will look like this: 

- Zope is only certified on using the HTTP server
- You are required to use an encryption proxy in front of it, to ensure
a trusted path to the user.
- A famous proxy is Apache with a certain standard configuration. 

We can even show how the configuration will look like with Apache, but
that very likely won't be certified as a secure Apache setup is totally
out of our scope. 

Christian

-- 
gocept gmbh & co. kg - schalaunische str. 6 - 06366 koethen - germany
www.gocept.com - ct at gocept.com - phone +49 3496 30 99 112 -
fax +49 3496 30 99 118 - zope and plone consulting and development
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://mail.zope.org/pipermail/zope3-dev/attachments/20051214/b739feb1/attachment.bin