On 28 January 2014 23:41, Andrea Pescetti wrote:
> On 26/01/2014 jan i wrote:
>
>> *.openoffice.org can only be used for services located on apache hosts,
>> we
>> cannot give the certificate to e.g. sourceforge.
>>
>
> OK. So this is clear: the fact that we do have a *.openoffice.orgcertificate
On 26/01/2014 jan i wrote:
*.openoffice.org can only be used for services located on apache hosts, we
cannot give the certificate to e.g. sourceforge.
OK. So this is clear: the fact that we do have a *.openoffice.org
certificate becomes irrelevant for this discussion since it cannot be
used
Am 01/26/2014 06:27 PM, schrieb jan i:
On 26 January 2014 16:54, Andrea Pescetti wrote:
On 23/01/2014 Roberto Galoppini wrote:
Time by time we receive end-users' requests asking why extensions. and
templates. don't run under HTTPS.
If we want to, SourceForge would be happy to install such ce
On 26 January 2014 16:54, Andrea Pescetti wrote:
> On 23/01/2014 Roberto Galoppini wrote:
>
>> Time by time we receive end-users' requests asking why extensions. and
>> templates. don't run under HTTPS.
>> If we want to, SourceForge would be happy to install such certificates.
>> Thoughts?
>>
>
>
On 23/01/2014 Roberto Galoppini wrote:
Time by time we receive end-users' requests asking why extensions. and
templates. don't run under HTTPS.
If we want to, SourceForge would be happy to install such certificates.
Thoughts?
It would make sense to have HTTPS on both those sites.
Infra managed
