TL;DR: Need yubikey-luks 0.5.1 in U18.10/Cosmic please. :-)
This is the relevant change that gets pulled-in:
https://github.com/cornelinux/yubikey-luks/issues/37
** Bug watch added: github.com/cornelinux/yubikey-luks/issues #37
https://github.com/cornelinux/yubikey-luks/issues/37
--
You rece
Took some additional digging, but already confirmed, and definitely
yubikey-luks side of the fence... it was using a non-public interface.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904162#15
Looks like there was some refactoring, and ostensibly this is fixed in a
later iteration of yubike
Possibly Guilhem (~7-guilhem / @7-guilhem here on Launchpad) could
confirm `/conf/conf.d/cryptroot` is officially/intentionally retired?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619921
Title:
Conclusion thus far: What I am seeing might be a new breakage of
yubikey-luks in U18.10/Cosmic.
I dug up an older Ubuntu system (U16.04.3 LTS) that is known-working
with Yubikey LUKS + Plymouth, and `/conf/conf.d/cryptroot` is present in
initramfs. Contents is one line, a target specification for
Interesting tidbits from Cosmic (U18.10), running with `splash` removed
from boot arguments (i.e. disable Plymouth splash).
Boot LUKS prompt display:
sed: /conf/conf.d/cryptroot: No such file or directory
... (unrelated LVMeta'd warning)
/scripts/local-top/cryptroot: line 218: fold:
Resurfaced in Cosmic (U18.10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1619921
Title:
Password Prompt for yubikey not showing in Plymouth
To manage notifications about this bug go to:
https://
@sdeziel -- I have tested on an Ivy Bridge era (i5-3427U) and Apollo
Lake era (N3350) system thus far. The former is covered by the Intel
20180312 release, the latter is not. If time permits I'll also test on a
Skylake system.
Everything seems to be working properly w/r2 updated microcode query an
Additional nuance:
On a netplan enabled system also using cloud-init (+ curtin), the same
assertion is made regarding how to disable network functionality tied to
cloud-init is mentioned in /etc/netplan/50-cloud-init.yaml ("… disable
via stanza in /etc/cloud/cloud.cfg.d/99-disable-network-config.c
** Also affects: netplan
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/1640635
Title:
cloud-init creates /etc/network/interfaces.d/50-cloud-init.cfg even
Public bug reported:
Once the post Spectre/Meltdown situation has stabilized, it would be
appreciated if that edition of Intel CPU microcode is backported into
Xenial / 16.04 LTS.
Thanks :-)
** Affects: intel-microcode (Ubuntu)
Importance: Undecided
Status: New
--
You received th
~ 2 years later ... :-)
For item 2, Intel now* documents what CPU family and stepping(s) are
covered by each "Intel Processor Microcode" data file bundle. However,
it would be better just point to the authoritative location, rather than
engaging in lots of copy-pasta (yes pun) from the upstream so
11 matches
Mail list logo
