[Bug 1972939] Re: Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes

[Nathan Stratton Treadway]

On Wed, May 18, 2022 at 13:41:06 -0000, Simon Chopin wrote:
> Also, does tinc work in a purely Jammy context? :-)

Sorry, I just realized that I had not mentioned here on this bug the
results of my tests between various Ubuntu versions.  I didn't test
Jammy-to-Jammy, but (briefly):

  * Jammy (1.0.36/libssl3) to Xenial (1.0.26/libssl1.0.0) fails

  * Impish (1.0.36/libssl1.1) works to both Jammy and Xenial (no
    openssl.cnf changes needed on any node)  

  * Focal (also 1.0.36/libssl1.1]) worked to Xenial. (I did not
    test that to Jammy.)
 
  * Jammy to Bionic (1.0.33/libssl1.1) works (no openssl.cnf changes
    needed)

(I did not test point-releases between Xenial and Bionic.)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1972939

Title:
  Jammy tinc  incompatibile with older (e.g. Xenial) tinc nodes

Status in Release Notes for Ubuntu:
  New
Status in openssl package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New

Bug description:
  The tinc included in Jammy (1.0.36-2build1 linked with libssl3) cannot
  connect to tinc nodes running e.g. tinc from Xenial (1.0.26-1).

  (Tinc from Impish, which is also v1.0.36-2 but is linked to libssl1.1,
  can connect to these nodes without problems.)

  The symptom is a log message (on the system running Jammy) during the
  metadata channel negotiation (with debug level set to 5):

  Error during initialisation of cipher from tinc_xenial [...]
  error:0308010C:digital envelope routines::unsupported

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1972939/+subscriptions