I just checked (by installation on a virtual machine) that a *virgin* (base 
+ destktop + usual utilities) debian stable (jessie) has openssl installed. 
Tentatively asking for its removal (apt-get remove -s openssl) tells that 
it would remove a ton of system utilities.

The same is true on testing (stretch).

Either Debian isn't aware of the situation (which would greatly surprise me 
after all this time) or ... the situation is not as bad as it looks to some.

More on this to follow : we ave several solutions (from loopholes to 
triumphal arches...).

--
Emmanuel Charpentier

Le jeudi 27 octobre 2016 16:59:02 UTC+2, Jean-Pierre Flori a écrit :
>
>
>
> On Thursday, October 27, 2016 at 4:49:23 PM UTC+2, Emmanuel Charpentier 
> wrote:
>>
>>
>>
>> Le jeudi 27 octobre 2016 16:04:52 UTC+2, Jean-Pierre Flori a écrit :
>>>
>>>
>>>
>>> On Thursday, October 27, 2016 at 3:59:26 PM UTC+2, Emmanuel Charpentier 
>>> wrote:
>>>>
>>>>
>>>>
>>>> Le jeudi 27 octobre 2016 13:10:17 UTC+2, François a écrit :
>>>>>
>>>>> It is a most interesting point because it explain why 
>>>>> the R binary installed from epel for RH7.1 and family 
>>>>> isn’t linked to openssl. 
>>>>>
>>>>
>>>> How old is RH7.1 ? The introduction of the libcurl requirement dates 
>>>> from the R 3.3.0 release, (May 3, 2016).
>>>>
>>>> I note that Debian (notoriously twitchy about license issues) didn't 
>>>> seem to have any qualms packaging 3.3.0, nor 3.3.1. 
>>>>
>>>  
>>> I'd say Debian links curl to GnuTLS.
>>>
>>
>> Probably not : My system's curl-config --protocols says that HTTPS: is 
>> supported. A trial of curl's configure --without-ssl --with-gnutls does not 
>> claim to support it (in the summary printed at th end of ./configure...).
>>
>> Are you sure you  installed the gnutls dev headers?
> GnuTLS provides an SSL implem, not just SSL.
>  
>
>> However, I'm not sure : Debian's blurb about libcurl3-gnutls says that it 
>> supports https, imaps, ldaps, smtps and pop3s.
>>
>> To be sure, I'll have to setup a virtual machine with a minimal 
>> environment (no openssl, of course) and try to setup libcurl (and, if 
>> successful, Sage) in that environment. This is time consuming, so not quite 
>> real soon...
>>
> You mean with gnutls?
> Or with no ssl/tls at all?
>
> I already did the latter and it works (modulo hacking R's configure).
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to