Closed gicmo closed 4 years ago
I think the only sane way to deal with this is to just blacklist this MAC address and refuse to let it be claimed or configured. At least until we have another system ID. Because the problem here is that the MAC has been claimed at some point, and we need to allow a MAC address to be configured from multiple IPs, in case a device is connected to a place without a static public IP.
That MAC address has been blacklisted and removed from provision.fedoraproject.org Thanks for the report!
I managed to compose and boot an Fedora IoT like image via osbuild (yay). When I booted it I was suprised to find that an ssh key got provisioned via
zezere-ignition
. This is of course because the qemu uses one very specific mac address (52:54:00:12:34:56
) as the default if non is specified (qemu net/net.c:182).I think it would make sense to special case that MAC address. Maybe set the root password to a well known one, or require a token for that MAC address (like in issue #54).