This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skrah
Recipients ajaksu2, nnorwitz, pitrou, skrah, tim.peters
Date 2010-04-09.15:38:02
SpamBayes Score 0.0035032057
Marked as misclassified No
Message-id <1270827485.94.0.25021658174.issue3581@psf.upfronthosting.co.za>
In-reply-to
Content
I reread http://www.ietf.org/rfc/rfc4122.txt and I'm pretty sure that
if getnode() is supposed to return a hardware address, one of the
following should be used:

  1) If ifconfig etc. returns successfully, we are fine.

  2) If uuid_generate_time() or UuidCreateSequential() are used
     to extract the node ID, we have to make sure that the returned
     UUID is in fact RFC_4122 and version 1.

  3) The fallback node ID should be 47 bits according to section 4.5.


I've got a new patch (getnode.patch) that takes care of these issues.
History
Date User Action Args
2010-04-09 15:38:06skrahsetrecipients: + skrah, tim.peters, nnorwitz, pitrou, ajaksu2
2010-04-09 15:38:05skrahsetmessageid: <1270827485.94.0.25021658174.issue3581@psf.upfronthosting.co.za>
2010-04-09 15:38:04skrahlinkissue3581 messages
2010-04-09 15:38:04skrahcreate