News for hackers. Stuff that matters.
Re:TIL: Versions of UUID and when to use them by Lammy on Sunday August 25, 2024 @04:47PM (#41351267)
> UUID Version 2 (v2) is reserved for security IDs with no known details.

Only no known details if the only document you're reading is the notoriously poorly-specified RFC. Here you go: https://pubs.opengroup.org/onlinepubs/9696989899/chap5.htm#t...

There are also “version 0” UUIDs that you are very unlikely to ever come across but should be noted because they are the source of the reserved bits (via wastefully setting aside an entire octet for Address Family) that later allowed the other “versions” to be specified in a compatible way. Read my research about them here in my UUID library: https://github.com/okeeblow/DistorteD/blob/NEW%E2%80%85SENSA...

I decided to support them Because It's Cool™ but still need to figure out how to handle the date rollover of them and the even-older Apollo UIDs:

  irb> ::GlobeGlitter::from_ncs_time
  => "#<GlobeGlitter 40639cd25341.02.00.00.e0.4c.18.00.69>"
  irb> ::GlobeGlitter::from_ncs_time.to_time
  => 1988-12-21 14:52:02 UTC
  irb> ::GlobeGlitter::from_aegis_time
  => "#<GlobeGlitter 00000000-0000-0000-4814-17c8b0080069>"

(Proper AEGIS `#to_str` not implemented yet lol)
Re:TIL: Versions of UUID and when to use them by kyzer-davis on Wednesday September 04, 2024 @05:34PM (#41451119)
> Only no known details if the only document you're reading is the notoriously poorly-specified RFC

To be fair, in RFC9562 I did cite two documents that are UUID Version 2 specifications. But RFC4122 was too cryptic for my taste.

As for the historical UUID types specified by the 0-7 Variant space: We are starting work on an informational RFC that will help folks understand those.

See https://github.com/yocto/draft-yocto-uuid if you want to add to some discussions and/or review text. We are still a bit early into the stages but I hope to have some progress soon.