On Mar 19, 2025, Hans wrote: > It is often leaving my LAN, because I am often on the road with my > laptop. And it is not the lan interface important, but the wifi > interface.
For clarification -- I was saying "your LAN" in the sense of "home", not in reference to the interface. > [...] > However, if the developers or maintainers think, everything is all > right and the user can change the mac manually when he wants it, and > when he forgot to do it, then he just simply had hard luck, who cares, > then we can close this discussion! Well, I can't speak for the devs / package maintainers -- I'm just a user afterall (as are nearly all of us here on debian-user ;) ) > > For myself the solution is "make manually on the road" (and maybe, if > I am lazy, I will create a script for me), but this solution is not > usable for everybody. share the script, then it is :) Honestly, I would imagine all that's needed is an "@reboot" definition in a cronjob that runs the macchanger command (or equivalent in systemd timer things). > > Short for long: I thought, I should mention this issue as it might be > interesting. If not, sorry for the noise. > > Best > > Hans > > Am Mittwoch, 19. März 2025, 10:31:26 CET schrieb Dan Purgert: > > On Mar 19, 2025, Hans wrote: > > > Hi Geert, > > > > > > the desired goal is, that my original MAC will never appear after > > > boot. As dpkg-reconfigure macchanger claims this to do, in real it > > > does not. > > > > Is this PC physically leaving your LAN? If not, changing the MAC isn't > > going to do all that much. > > > > > My background thouhgts are: When using maachanger in TAILS, then it > > > will never protect the victim. > > > > I'm not a user of tails, but I would imagine that they've "fixed" the > > gap. If not, maybe bring it up to their maintainers? > > > > That being said -- protect the "victim" from what, exactly? > > > > -- |_|O|_| |_|_|O| Github: https://github.com/dpurgert |O|O|O| PGP: DDAB 23FB 19FA 7D85 1CC1 E067 6D65 70E5 4CE7 2860
signature.asc
Description: PGP signature
