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

[Simon Chopin]

** Changed in: tinc (Ubuntu)
       Status: New => Confirmed

** Changed in: tinc (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: openssl (Ubuntu)
       Status: New => Confirmed

** Also affects: openssl (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Also affects: tinc (Ubuntu Jammy)
   Importance: Undecided
       Status: New

** Changed in: openssl (Ubuntu Jammy)
       Status: New => Confirmed

** Changed in: tinc (Ubuntu Jammy)
       Status: New => Invalid

** Changed in: openssl (Ubuntu)
       Status: Confirmed => Fix Released

-- 
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:
  Fix Released
Status in tinc package in Ubuntu:
  Invalid
Status in openssl source package in Jammy:
  Confirmed
Status in tinc source package in Jammy:
  Invalid

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