Chris, what you're describing is out of scope of the this launchpad
issue. It is purely to address the invalid alg selected when running in
fips mode. What you're describing is likely a result of the hmac
implementation of tmp2-tools's tpm2-tss, likely described here:
https://github.com/tpm2-softw
It should exist if running the fips kernel and fips=1 is set as a
cmdline opt. It sets after the tcrypt tests run iirc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073429
Title:
Jammy clevis forc
Public bug reported:
[Summary]
On Sep 12, cloud-tuned kernels promoted from 6.5->6.8 for 22.04. After this,
Jammy CVM instances began experiencing a kernel panic post-reboot. The direct
kernel panic regarding locating root part is seemingly a symptom of the actual
problem with the initramfs dec
Public bug reported:
Noticed while attempting to upgrade jammy linux-gcp 6.5 -> 6.8.
Typical upgrade flow for most users is to just use `apt upgrade` these
days, but this does not currently work due to a recommends on ubuntu-
kernel-accessories from linux-gcp. This seems to be the case for all
cl
Or maybe this is a problem with gvenic not handling this correctly, as
this should `just work` as I understand it after speaking with a few
colleagues (even with the bridge mtu delta)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
gvenic instances seem to have an mtu of 1460 by default. If you `lxd
init --auto` and then `ip link set mtu 1460 lxdbr0`, then the launched
containers should work. I think lxd init should account for the fact
that not all interfaces are 1500 by default.
--
You received this bug notification becau
Public bug reported:
[Current Behavior]
Users still on Kinetic and Lunar are prompted to upgrade to Noble via the motd,
however d-r-u claims that upgrading from those releases -> noble is
unsupported. You also can not upgrade to mantic anymore, so you would need to
manually change your sources
I think I made the patch file correctly..
** Patch added: "luks.patch"
https://bugs.launchpad.net/ubuntu/jammy/+source/clevis/+bug/2073429/+attachment/5798147/+files/luks.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
Hello,
clevis released with version 18 on jammy (22.04). For reasons that are a
bit beyond me, the cryptsetup call inside of clevis creates keyslots
using argon2id as the pbkdf. While most folks would say this is
preferable, NIST still has not approved it and it is thus incom
