[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ronald Oussoren added the comment: @terrygreeniaus: Are you running macOS 11 on your MacBook Pro? If so, could you verify the hardware address of the iBridge interface? I've checked to libc sources on opensource.apple.com and those don't seem to contain code to treat the iBridge interface s

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ronald Oussoren added the comment: I got feedback on FB889: Apple says they have fixed the issue (they don't mention in what version, but I expect 11.2). I haven't checked this yet. -- ___ Python tracker __

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ronald Oussoren added the comment: the most recent UUID implementation on opensource.apple.com: https://opensource.apple.com/source/Libc/Libc-1353.100.2/uuid/uuidsrc/gen_uuid.c.auto.html The implementation of get_node_id() doesn't ignore the iBridge interface, which means uuid_generate_time(

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ronald Oussoren added the comment: An option is to use the host UUID instead of libuuid (as used by the _uuid extension). This has two problems though: (1) the RFC prescribes that the node id is a IEEE 802 MAC address, and (2) the host UUID is a full UUID and would have to be post processed.

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ronald Oussoren added the comment: I've verified that python 3.8 and 3.9 use the system uuid functions (part of libsystem). This means this issue might not be fixable without dropping the use of the _uuid extension. @terrygreeniaus: Can you still reproduce this issue? If so, does "import _

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Vedran Čačić added the comment: Yes, you're right. Xoring can be replaced by any key-derivation function, though of course that's probably overkill. -- ___ Python tracker ___

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Change by Jeffrey Kintscher : -- nosy: +Jeffrey.Kintscher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: htt

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Terry Greeniaus added the comment: xoring does not guarantee uniqueness and has a good chance of discarding it, so it seems like a bad idea to me. Suppose I have exactly two adapters with MAC addresses 0 and 3. Suppose you have exactly two adapters with MAC addresses 1 and 2. We'll both xor

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Vedran Čačić added the comment: +1 on xoring all MAC addresses to get NodeID. Since it is only done once at import time, it shouldn't be too expensive (many other things including OS calls are done at initialization). But yes, if the problem goes away with new version of _uuid, then the fix i

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ronald Oussoren added the comment: Note that recent commits to the trunk and 3.8 and 3.9 branches have added a _uuid module using libuuid (and the comparable Windows API). I'd expect that this extension will also be used on macOS. I'd advise to check if this issue is still present when using

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Rémi Lapeyre added the comment: > The question then is: is there any way for the uuid module to recognize and > ignore such interfaces other than by the hardcoded MAC address? Could uuid1 xor all mac addresses on MacOS? The result would be deterministic and unique as long as there is at least

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Vedran Čačić added the comment: I'd like to point out that _even_ if you do reuse MAC address: 1. node IDs don't have to be derived from MAC addresses only (though in practice they usually are - I'm just saying the RFC gives you permission to include other information in it). 2. The time res

[issue41552] uuid.uuid1() on certain Macs does not generate unique IDs

Ned Deily added the comment: FWIW, I see similar behavior on a 2017 MBP running with 10.15.6 or 11.0 (Big Sur) beta 4. That's ... odd that there is a non-unique MAC address. (Not surprisingly, there is no such problem on an iMac that doesn't have the touchbar subsystem.) That particular inte