[New-bugs-announce] [issue31643] test_uuid: test_getnode and test_windll_getnode fail if connected to the Internet via an Android phone

Ivan Pozdeev report at bugs.python.org
Fri Sep 29 17:37:18 EDT 2017


New submission from Ivan Pozdeev <ivan_pozdeev at mail.ru>:

Ethernet emulation for some devices like Android phones' tethering use all-zero MAC addresses (which is okay since they don't actually pass Ethernet frames to other NICs). This results in a node ID of 0 if I'm currently connected to the Net via such a device. Which fails range checks in the corresponding tests.

RFC 4122 doesn't actually have any prohibitions of using a node ID of 0. Neither does IEEE 802.3 (or rather, whatever info I gathered on it since the standard's text is not freely available) assign any special meaning to an all-zero MAC address.

The patch also corrects the check call in test_windll_getnode since the tested function always generates UUID from a MAC address.

----------
components: Tests
files: 0001-Allow-for-all-zero-MAC-based-node-ID-e.g.-mobile-mod.patch
keywords: patch
messages: 303360
nosy: Ivan.Pozdeev
priority: normal
severity: normal
status: open
title: test_uuid: test_getnode and test_windll_getnode fail if connected to the Internet via an Android phone
type: behavior
versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6, Python 3.7, Python 3.8
Added file: https://bugs.python.org/file47178/0001-Allow-for-all-zero-MAC-based-node-ID-e.g.-mobile-mod.patch

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31643>
_______________________________________


More information about the New-bugs-announce mailing list