You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems - oddly enough - to be a tad non-trivial to enable hostnames for resolving the keyserver in initramfs. Furthermore it seems to work just fine, if it's using DHCP. I'm probably overlooking something here.
In any case, I'd deem it a useful capability. A proper hostname should make the setup more durable. ATM if the IP of the keyserver is changed, the scripts and the initrd need to be modified. I think if we have a hostname (and it's referenced in the KnownHosts) we can move the keyserver around without breaking unlock capability on every system.
The text was updated successfully, but these errors were encountered:
Yes, I read this too. But it surprises me a little. Using DHCP, it seems to work fine. This does not sound like a library problem to me. But we should really dig into this. Maybe adjusting/supplying a proper resolv.conf already works.
It seems - oddly enough - to be a tad non-trivial to enable hostnames for resolving the keyserver in initramfs. Furthermore it seems to work just fine, if it's using DHCP. I'm probably overlooking something here.
In any case, I'd deem it a useful capability. A proper hostname should make the setup more durable. ATM if the IP of the keyserver is changed, the scripts and the initrd need to be modified. I think if we have a hostname (and it's referenced in the
KnownHosts
) we can move the keyserver around without breaking unlock capability on every system.The text was updated successfully, but these errors were encountered: