4 ms·
Especially since it contains Mac addresses, which are very much not random, encoding such info as the manufacturer of the device. Yes, these can be randomized,
by djha-skin 3y ago
Especially since it contains Mac addresses, which are very much not random, encoding such info as the manufacturer of the device. Yes, these can be randomized, but you don't generally want to do this with servers. You want to know the Mac of your box. You certainly don't want to leak it or show bad actors what subnet it's in. Again, the non-mac part of the numbers leak information; they are very much not random.
- greyface- 3y agoThis has not been the case since RFC8064 (2017). Modern systems use stable, non-MAC-based IIDs. https://datatracker.ietf.org/doc/html/rfc8064 https://datatracker.ietf.org/doc/html/rfc8064
- throw0101c 3y agoActually 2001: * https://datatracker.ietf.org/doc/html/rfc3041 https://datatracker.ietf.org/doc/html/rfc3041 Updated in 2007: * https://datatracker.ietf.org/doc/html/rfc4941 https://datatracker.ietf.org/doc/html/rfc4941
- throw0101c 3y ago> Especially since it contains Mac addresses, which are very much not random, encoding such info as the manufacturer of the device. Yes, these can be randomized, but you don't generally want to do this with servers. You also don't have to use the MAC-based addresses on the server either. You can generate a random address and use that for your service. Or you can regularly generate addresses on the server and update DNS so that the service has a new address every x hours or days. Or you could have the server not have any 'public' addresses, and whenever a new client wants to connect a new address is generated just for that client (with a TTL).