On Wed, May 18, 2022 at 13:41:06 -, 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
On Wed, May 18, 2022 at 13:37:46 -, Simon Chopin wrote:
> Could you give more details about what happens when using the legacy
> providers?
The short version is that by enabling the legacy provider and setting
SECLEVEL to 1, I'm able to get past the "digital envelope
routines::unsupported"
On Wed, May 18, 2022 at 13:41:06 -, Simon Chopin wrote:
> Also, does tinc work in a purely Jammy context? :-)
As far as I can determine the issue relates to compatibility between
libssl3 and the algorithms used by the Xenial-era tinc, and thus I can't
imagine Jammy-to-Jammy would be a
Also, does tinc work in a purely Jammy context? :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972939
Title:
Jammy tinc incompatibile with older (e.g. Xenial) tinc nodes
To manage
Could you give more details about what happens when using the legacy
providers?
** Changed in: tinc (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972939
On Wed, May 18, 2022 at 07:42:04 -, Simon Chopin wrote:
> I'm guessing there are some SSL certificates involved? If so, this issue
Tinc uses openssl's implementations of specific alogorithms, but does not
use either TLS or SSL certificates. (So I don't think the Tinc situation
is covered by
I'm guessing there are some SSL certificates involved? If so, this issue
is mentioned in the release notes: certificates that use e.g. SHA1 as
the digest algorithm should be re-issued by your provider with a
stronger hash algorithm.
Would you be able to check that it is the correct diagnostic?
If
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972939
Title:
Jammy tinc incompatibile with older (e.g. Xenial) tinc
Since the tinc version number in Focal/Impish and Jammy are the same, it
might be worth adding a warning to the release notes to people don't
unexpectedly loose VPN access by upgrading to Jammy. (Or explaining a
workaround, if one can be determined.)
** Package changed: tinc (Ubuntu) =>