Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openoffice.apache.org
MIME-Version: 1.0
In-Reply-To: <51AE4FB1.2050809@apache.org>
References: 
 <CAK2iWdQYmRR2=KEkc2zrchPpFDKF2QV8ZyKCY3qvAJP8pK+FQA@mail.gmail.com>
	<51AC655D.1020106@googlemail.com>
	<CAK2iWdRXqCQKXAxQDHd8Wm3C_3o6MCdWMpA5OQp7WJyXDhfc0g@mail.gmail.com>
	<51AC87D6.5050201@googlemail.com>
	<CAP-ksohjj83Yj7FChEFx3TodAw0ud7UsvuyYxYYA385RvPHEOg@mail.gmail.com>
	<51AE4FB1.2050809@apache.org>
Date: Tue, 4 Jun 2013 23:59:02 +0200
Message-ID: 
 <CAK2iWdSAw5cQ_RPC_Gwkh0AVVf+KEV9sxuiMA2r_S2==Jjnfjg@mail.gmail.com>
Subject: Re: updates.openoffice.org
From: janI <jani@apache.org>
To: dev@openoffice.apache.org
Content-Type: multipart/alternative; boundary=001a11c37d7665abb804de5b3049

--001a11c37d7665abb804de5b3049
Content-Type: text/plain; charset=ISO-8859-1

On 4 June 2013 22:36, Andrea Pescetti <pescetti@apache.org> wrote:

> On 03/06/2013 Rob Weir wrote:
>
>> I think the concern is this:
>> 1) We want SSL for 4.0.http://update.openoffice.**org<http://update.openoffice.org> is not HTTPS.
>>
>> 2) The URL https://ooo-site.openoffice.**apache.org<https://ooo-site.openoffice.apache.org> supports SSL, but is
>> not considered "long term stable".  The URL is an artifact of the CMS
>> 3) We're looking for a stable URL.  One could be
>> https://updates.openoffice.org**, but that requires an SSL cert for
>> *.openoffice.org.  But will that be supported in time for the AOO 4.0
>> release?
>> 4) Backup plan is updates.openoffice.apache.org, which could be
>> supported via SSL today, using the *.apache.org cert.  If we do that
>> we'd want to map that to its own CMS dir in SVN. so it can be updated
>> and published via the CMS.
>>
>
> This is mostly correct, except the fact (in #2 and #4) that the current
> certificates only support x.apache.org and not x.y.apache.org: so
> https://ooo-site.apache.org is what is in the sources right now (well,
> the last time I checked) and https://openoffice-updates.**apache.org<https://openoffice-updates.apache.org>(or something like that) should be used for the backup plan in #4.
>

Hi

I am confused, it seem we nearly all agree on
https://updates.openoffice.orgbut not on the directory.

The order for the cert is being processed, when the cert arrives it needs
to be implemented on erebus-sll (our https: proxy), and we (infra) need to
do some updates on the aoo servers.

In order to do this work, I need:

1) which url (e.g. https://updates.openoffice.org)
2) should relate to which directory in svn.

The last mails contains different proposal ranging from dont do it for 4.0
to different dirs, that is something I cannot implement.

We can also decide to forget it for https:updates.*, but I need a single
decision to be able to implement it.

rgds
jan I.

>
> Regards,
>   Andrea.
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<dev-unsubscribe@openoffice.apache.org>
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>

--001a11c37d7665abb804de5b3049--