On Feb 9, 2013, at 21:49, Phil Dobbin wrote: > On 02/09/2013 12:04 PM, Rainer Müller wrote: > >> On 2013-02-09 01:59, Clemens Lang wrote: >>> On Sat, Feb 09, 2013 at 01:48:53AM +0100, Clemens Lang wrote: >>>> just a quick warning that the update of openssl to 1.0.1d breaks >>>> MacPorts OpenSSH in the sense that connecting to other machines using >>>> the ssh client is no longer possible. Rebuilding openssh does not fix >>>> this. I haven't had any time to investigate, though. >>> >>> Sounds like >>> http://rt.openssl.org/Ticket/Display.html?id=2975&user=guest&pass=guest. >>> You might want to wait with updating your openssl until this is solved. >> >> There are also problems reported with 1.0.1d from the tor project: >> https://trac.torproject.org/projects/tor/ticket/8179 >> >> Should we revert to 1.0.1c or backport the relevant fixes from git? >> I would rather go back to an older, working version instead of fiddling >> with the code. > > I've just ran selfupdate & seen that openssl 1.0.1d is included in the > update. > > I take it this means it's OK to run the update?
It means what it says above: you may want to wait to update openssl until this issue is resolved. Or perhaps the issue does not affect you, if you are not using openssh or tor. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
