© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hi Joost,
putting 2.4.4 into Trusty would be a major change with too much of a regression risk for others.
See [1] for Details. We would need to find the actual issue you are hitting and then the fix that fixed it between 2.3.2-7ubuntu3.2 -> 2.4.4 to backport just the fix under the constraints of [1].
As you say, upgrading 16.04 is an option as there you opt-in to take the potential regressions of an upgrade (but you usually get way more improvements than regressions, but people see what causes work for them :-) ).
In general on authentication rejects due to version upgrades what I've seen in the past is that the list of supported encryptions bweteen server and client no more has a shared element that can be used. But it can very well be something completely different.
So we need to check what we can find once you have the error.
As much as possible use verbose logging and report the client and server logs of the same case.
That should make it easier to find the root cause.
[1]: https:/