Hi,

> On 17 Aug 2019, at 12:09 pm, Dmitri Zaitsev <[email protected]> wrote:
> 
> Hi Chris,
> 
> I understand that MacPorts are supporting old versions going back to Tiger 
> and some of the stats confirm users' downloads. I do appreciate the advice to 
> upgrade but there can be many personal reasons why people prefer to stay with 
> their older systems. It is however not at all obvious that a plain upgrade to 
> some later supported OS would actually fix that problem, so having an 
> alternative would help all these users, and as you mention it is entirely 
> within the MacPorts system that some older `ssl` is used internally for some 
> reason, instead of the more recent available one that could have been used 
> instead, in which case the problem might have not existed.

what OS you run is of course your choice. I gave my advice and you are free to 
take or leave it.

In this case though, upgrading your OS would absolutely 100% fix your SSL 
problems though, as these are completely specific to running out-of-date 
systems.

Chris

> 
> I do appreciate your time and fully understand that this is not your concern 
> but would be still thankful if anyone could advice on how to configure 
> MacPorts to use the recent ssl.
> 
> Cheers,
> Dmitri.
> 
> 
> 
> 
> On Saturday, August 17, 2019, Christopher Jones <[email protected] 
> <mailto:[email protected]>> wrote:
> Hi,
> 
> First, please keep the discussion on the mailing list.
> 
> just installing the up to date ports for openssl etc. is not enough, as by 
> default the fetches macports performs will not use these. 
> 
> I believe there are ways to bootstrap macports to do this, but as I have no 
> need of it (I don’t run such old OSes myself, apart from in VMs for test 
> purposes) I cannot comment on how that is done.
> 
> ( Updating your OS is really the best option, if your hardware supports a new 
> OSes. 10.8 hs not received any security updates for quite a while now…. )
> 
> cheers Chris 
> 
>> On 17 Aug 2019, at 11:48 am, Dmitri Zaitsev <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> Thank you!
>> 
>> I am trying to understand the cause and it seems my both openssl and ssh are 
>> recent.
>> Any other idea where to look for (other than OS upgrading :-)?
>> 
>> https://trac.macports.org/ticket/58848#comment:4 
>> <https://trac.macports.org/ticket/58848#comment:4>
>> 
>> 
>> On Saturday, August 17, 2019, Christopher Jones <[email protected] 
>> <mailto:[email protected]>> wrote:
>> Hi,
>> 
>> I have commented on both tickets. They are in essence the same problem, the 
>> out of date SSL support in macOS10.8 that is causing you https fetch issues.
>> 
>> cheers Chris
>> 
>>> On 17 Aug 2019, at 11:06 am, Dmitri Zaitsev <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> Please see 
>>> https://trac.macports.org/ticket/58847 
>>> <https://trac.macports.org/ticket/58847>
>>> https://trac.macports.org/ticket/58848 
>>> <https://trac.macports.org/ticket/58848>
>>> 
>>> I have managed to get around the first one by manually downloading the 
>>> file, but have no idea what to do about the second, which might have the 
>>> same cause (failed downloads).
>>> 
>>> Any hint is appreciated.
>>> 
>>> 
>>> On Saturday, August 17, 2019, Ryan Schmidt <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> 
>>> On Aug 16, 2019, at 02:14, Dmitri Zaitsev wrote:
>>> 
>>> > Unfortunately it got worse, I can't install any port at all now. :(
>>> 
>>> Sorry to hear that... can you provide any more details?
>>> 
>>> 
>>> 
>>> -- 
>>> Dmitri Zaitsev
>>> School of Mathematics
>>> Trinity College Dublin
>>> 
>>> WWW:  http://www.maths.tcd.ie/~zaitsev/ <http://www.maths.tcd.ie/~zaitsev/>
>>> 
>> 
>> 
>> 
>> -- 
>> Dmitri Zaitsev
>> School of Mathematics
>> Trinity College Dublin
>> 
>> WWW:  http://www.maths.tcd.ie/~zaitsev/ <http://www.maths.tcd.ie/~zaitsev/>
>> 
> 
> 
> 
> -- 
> Dmitri Zaitsev
> School of Mathematics
> Trinity College Dublin
> 
> WWW:  http://www.maths.tcd.ie/~zaitsev/ <http://www.maths.tcd.ie/~zaitsev/>
> 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to