Hi @juliank,

Upon further discussion with the team, I was informed that this security fix 
wasn't backported to Resolute, and it was agreed upon that it can be part of 
the SRU with the security team.
As this issue isn't on Resolute (it was introduced by 
https://github.com/canonical/authd/pull/1546 ("Lines changed: 3488 additions & 
728 deletions") which is part of this SRU "Use stable provider IDs to help 
match users to their existing local accounts when their email address or 
username changes."

So this approach (only fixing the security issue via the security pocket
in Stonking and waiting for the SRU to get it fixed in Resolute) was
agreed upon with Security, given the CVE is only of medium severity.

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

Title:
  SRU(Resolute): Update authd to 0.7.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/authd/+bug/2173548/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to