3 ms·
I'm really excited to see k-sortable unique identifiers (flakes) be submitted as an IETF draft. This will help keep the UUID data type relevant. However, I'd
by politician 5y ago
I'm really excited to see k-sortable unique identifiers (flakes) be submitted as an IETF draft. This will help keep the UUID data type relevant.
However, I'd like to see the draft include a mention about the practice of embedding machine and data type identifiers into the format which helps in distributed applications.
- cratermoon 5y agothe practice of embedding machine and data type identifiers into the format is a security risk
- emodendroket 5y agoHow do you figure? There's no guarantee guids aren't supposed to be predictable, right?
- lazide 5y agoFor one? It allows you to figure out which machine is generating UUIDs, how fast, and all UUIDs it has ever generated. Which 1) is info leakage that is useful to many people in many ways, 2) can be a security risk as it tells you who to attack. 3) at a minimum is a privacy risk.
- politician 5y agoIt might be, but whether it is depends on your threat model. If you need to obscure both when in time and where in space, then UUIDv4 is a better option.
- pjscott 5y agoSection 7, "Distributed UUID Generation", mentions that you MAY hold some of the most significant random bits constant per-machine to act as a machine identifier.