Rudder

Currently I think it is easily possible for one host to inject / overwrite a different system's inventory data.
It should already be possible to set up different curl user accounts for different network segments, but that needs modification of the system techniques, which isn't fun either.

Goal would be for a host not to be able to send inventory for another host. Most importantly not for one attached to a different rudder relay / root, and ideally also not even for any other system.
The protection of root & relay against such misuse should probably also be checked, no idea if they accept inventory data for themselves over the "client" channel.

I'll not muse about ways to do it.

Note:
There's an obvious edge case with reinstall-with-different uuid; but that case already exists and already causes slight problems when it happens.
(uuid conflicts, name conflicts, both need to be considered and different things happen)