[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Savannah-help-public] Cryptographic software legal notice
From: |
Eran Strod |
Subject: |
Re: [Savannah-help-public] Cryptographic software legal notice |
Date: |
Tue, 29 Sep 2009 19:48:56 -0400 |
Does Savannah have a legal person who could answer a question about
this legal notice?
---
Eran Strod
address@hidden
On Sep 28, 2009, at 5:19 PM, Sylvain Beucler wrote:
> I updated the link, it's not seriously to rely on old mod_rewrite
> redirections ;)
>
> --
> Sylvain
>
> On Fri, Sep 25, 2009 at 12:08:34AM +0200, Karl Berry wrote:
>> Hi Eran,
>>
>> (Stay on-list please, for posterity. Your reply included below ....)
>>
>> It works if I use http instead of https.
>>
>> I think you are right that it would be better to use http instead of
>> https in the "Cryptographic software legal notice" link on the
>> savannah
>> home page. I don't see any reason not to, but some other savannah
>> person does.
>>
>> If you want to actually do anything with savannah, though, you're
>> going
>> to have to add either our certificate or the cacert root
>> certificate to
>> your browser: http://savannah.gnu.org/tls/
>>
>> Best,
>> Karl
>>
>>
>> Date: Thu, 24 Sep 2009 09:18:59 -0400
>> From: Eran Strod <address@hidden>
>> To: Karl Berry <address@hidden>
>> Subject: Re: [Savannah-help-public] Cryptographic software legal
>> notice
>>
>>
>> Greetings Karl,
>>
>> First, thanks so much for getting back to me.
>>
>> The link from the home page redirects to:
>> https://savannah.gnu.org/faq/?admin=&group_id=5802&question=Savannah_-_Is_there_any_restriction_on_cryptographic_software.txt
>>
>> When I try to go there it gives me this error:
>>
>> You have asked Firefox to connect
>> securely to savannah.gnu.org, but we can't confirm that your
>> connection is secure.
>> Normally, when you try to connect securely,
>> sites will present trusted identification to prove that you are
>> going to the right place. However, this site's identity can't be
>> verified.
>>
>> It works if I use http instead of https.
>>
>> Do you think this is a problem on our side or does it make sense to
>> address it by changing the link on your page?
>>
>> Thanks,
>>
>>