Repository navigation
Select a stable machine identity from network adapters - #605
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Selecting the first network interface can produce an unusable or changing device identity. Choose a validated MAC address deterministically, prefer physical adapters, and cache the identity so authentication, bag requests, and downloads use the same value throughout a run.
Use IOKit hardware addresses on macOS, permanent adapter addresses when available on Windows, and sysfs metadata on Linux. Preserve macOS 27 redacted-address recovery and valid-address fallbacks for VMs and containers. Add regression coverage for adapter selection, invalid addresses, and concurrent lookups.