You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Andreas Hartmann <an...@apache.org> on 2008/02/21 23:26:15 UTC
SSL for docu pub (was: SSL encryption for usecases, inheriting to
sub-pages)
Jörn Nettingsmeier schrieb:
[...]
> :), but we should not introduce inheritance and complicated lookup
> mechanisms.
> there's the potentially dangerous situation when a page that should have
> ssl (and was in an ssl subtree) gets moved out of it and loses ssl
> protection - too many subtle pitfalls imho.
I just noticed that the SSL setting is already inherited. The docu
publication just used the default pub's policies directory and therefore
my change to the policy had no effect.
The questions is how we should set up the zones server for SSL. Maybe
the easiest way is to use the servlet container. Is there already a
certificate that we can use?
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: SSL for docu pub
Posted by Andreas Hartmann <an...@apache.org>.
Thorsten Scherler schrieb:
> On Thu, 2008-02-21 at 23:26 +0100, Andreas Hartmann wrote:
>> Jörn Nettingsmeier schrieb:
>>
>> [...]
>>
>>> :), but we should not introduce inheritance and complicated lookup
>>> mechanisms.
>>> there's the potentially dangerous situation when a page that should have
>>> ssl (and was in an ssl subtree) gets moved out of it and loses ssl
>>> protection - too many subtle pitfalls imho.
>> I just noticed that the SSL setting is already inherited. The docu
>> publication just used the default pub's policies directory and therefore
>> my change to the policy had no effect.
>>
>> The questions is how we should set up the zones server for SSL. Maybe
>> the easiest way is to use the servlet container. Is there already a
>> certificate that we can use?
>
> We need to ask this on the infrastructurer list, I am not aware of
> this.
Should we put a detailed concept paper in the Wiki so that they can
imagine what we are planning? This way they can decide whether to
endorse our publishing project.
> We may want to activate ssl in the apache and use it as well as proxy.
> This way we have a nice testing scenario with proxy as well on the zones
> server. Has the big advantages that all committer have access to it.
+1
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org
Re: SSL for docu pub (was: SSL encryption for usecases, inheriting
to sub-pages)
Posted by Thorsten Scherler <th...@apache.org>.
On Thu, 2008-02-21 at 23:26 +0100, Andreas Hartmann wrote:
> Jörn Nettingsmeier schrieb:
>
> [...]
>
> > :), but we should not introduce inheritance and complicated lookup
> > mechanisms.
> > there's the potentially dangerous situation when a page that should have
> > ssl (and was in an ssl subtree) gets moved out of it and loses ssl
> > protection - too many subtle pitfalls imho.
>
> I just noticed that the SSL setting is already inherited. The docu
> publication just used the default pub's policies directory and therefore
> my change to the policy had no effect.
>
> The questions is how we should set up the zones server for SSL. Maybe
> the easiest way is to use the servlet container. Is there already a
> certificate that we can use?
We need to ask this on the infrastructurer list, I am not aware of
this.
We may want to activate ssl in the apache and use it as well as proxy.
This way we have a nice testing scenario with proxy as well on the zones
server. Has the big advantages that all committer have access to it.
salu2
>
> -- Andreas
>
>
>
>
--
Thorsten Scherler thorsten.at.apache.org
Open Source Java consulting, training and solutions
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lenya.apache.org
For additional commands, e-mail: dev-help@lenya.apache.org