Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#59021 - [macchanger] flags -a|-A|-r don't change mac addresses...

Attached to Project: Community Packages
Opened by drathir (drathir) - Friday, 15 June 2018, 12:29 GMT
Last edited by Kyle Keen (keenerd) - Tuesday, 20 November 2018, 14:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Looks like package is broken somehow, bc -A option give always the same mac output similar is with -r option, but there is different to previous flag one mac but always the same too...

Additional info:
* package version(s)
community/macchanger 1.7.0-2 [installed]
* config and/or log files etc.
for macchanger -A device is always : 00:14:2f:a2:XX:XX (WildPackets)
for macchanger -r device is always : a2:97:a2:55:XX:XX (unknown)


Steps to reproduce:
just:
macchanger -A device
or
macchanger -r device

Greetings...
This task depends upon

Closed by  Kyle Keen (keenerd)
Tuesday, 20 November 2018, 14:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  macchanger 1.7.0-4
Comment by Doug Newgard (Scimmia) - Monday, 18 June 2018, 14:40 GMT
That sounds ... normal?
Comment by drathir (drathir) - Monday, 18 June 2018, 16:04 GMT
@Scimmia Nope not sounds normal, it should generate random addresses on every use not one and the same address...
Comment by drathir (drathir) - Friday, 16 November 2018, 23:06 GMT
Looks like something changed now not two static mac addresses are in use, but pool of 4 static mac addresses no matter of flag/switch type in use, which still is incorrect behavior for chosen options switches...
Comment by Kyle Keen (keenerd) - Tuesday, 20 November 2018, 14:13 GMT
It appears that the random seed is constrained to the range 32764-32767. This is caused by successfully (?) reading /dev/hwrng. Replacing this with /dev/random fixes the issue.

Loading...