Package: libssl1.0.0
Version: 1.0.1e-5
Severity: critical
Upgrading OpenSSL caused SSH to break.
Here's the upgrade from aptitude's log:
[UPGRADE] libssl-dev:amd64 1.0.1e-4 - 1.0.1e-5
[UPGRADE] libssl1.0.0:amd64 1.0.1e-4 - 1.0.1e-5
[UPGRADE] openssl:amd64 1.0.1e-4 - 1.0.1e-5
And here's SSH
On Sun, Dec 22, 2013 at 14:02:37 -0800, Josh Triplett wrote:
Package: libssl1.0.0
Version: 1.0.1e-5
Severity: critical
Upgrading OpenSSL caused SSH to break.
Here's the upgrade from aptitude's log:
[UPGRADE] libssl-dev:amd64 1.0.1e-4 - 1.0.1e-5
[UPGRADE] libssl1.0.0:amd64 1.0.1e-4 -
Package: libssl1.0.0
Version: 1.0.1e-5
Followup-For: Bug #732940
Julien Cristau wrote:
On Sun, Dec 22, 2013 at 14:02:37 -0800, Josh Triplett wrote:
Package: libssl1.0.0
Version: 1.0.1e-5
Severity: critical
Upgrading OpenSSL caused SSH to break.
Here's the upgrade from aptitude's log:
On Sun, Dec 22, 2013 at 02:16:43PM -0800, Josh Triplett wrote:
Package: libssl1.0.0
Version: 1.0.1e-5
Followup-For: Bug #732940
Julien Cristau wrote:
On Sun, Dec 22, 2013 at 14:02:37 -0800, Josh Triplett wrote:
Package: libssl1.0.0
Version: 1.0.1e-5
Severity: critical
Upgrading
Package: libssl1.0.0
Version: 1.0.1e-5
Followup-For: Bug #732940
Kurt Roeckx wrote:
On Sun, Dec 22, 2013 at 02:16:43PM -0800, Josh Triplett wrote:
Package: libssl1.0.0
Version: 1.0.1e-5
Followup-For: Bug #732940
Julien Cristau wrote:
On Sun, Dec 22, 2013 at 14:02:37 -0800, Josh Triplett
On Sun, Dec 22, 2013 at 02:45:32PM -0800, Josh Triplett wrote:
It's not OK to break forward compatibility without changing SONAME.
Software built against an older version of a library must always work
with a newer version that has the same SONAME; that's what the SONAME
exists for. It'd be
On 2013-12-22 23:08 +0100, Julien Cristau wrote:
On Sun, Dec 22, 2013 at 14:02:37 -0800, Josh Triplett wrote:
Package: libssl1.0.0
Version: 1.0.1e-5
Severity: critical
Upgrading OpenSSL caused SSH to break.
Here's the upgrade from aptitude's log:
[UPGRADE] libssl-dev:amd64 1.0.1e-4 -
Josh Triplett wrote:
I upgraded OpenSSL and OpenSSH stopped working. Since the SONAME didn't
change, kinda by definition this seems like a bug in OpenSSL, not
OpenSSH.
That by definition only holds if you assume all applications are
perfect software with no bugs whatsoever, and use libraries
Package: libssl1.0.0
Version: 1.0.1e-5
Followup-For: Bug #732940
Kurt Roeckx wrote:
On Sun, Dec 22, 2013 at 02:45:32PM -0800, Josh Triplett wrote:
It's not OK to break forward compatibility without changing SONAME.
Software built against an older version of a library must always work
with a
9 matches
Mail list logo