Sys-net: random MAC spoofing and random hostname (optional) automated on every boot without installing anything

[bien-vienido-qubes]

Random mac on sys-net, some moderators in a post didn’t criticize it — why?

Look at this post about mac spoofing using sys-net, where it uses macchanger with the -r (random) option and also -A with OUI:

Using macchanger for MAC‑spoofing on a sys‑net VM to prevent ISPs from collecting metadata that could be sold or handed over to governments

Introduction When you connect directly to the router that the ISP provides, the ISP can collect the metadata that you are using certain devices. This is an important piece of metadata that can be used to deanonymize you through correlation even if you’re using Tor, Whonix, etc. When you connect the sys‑net, the original MAC address of your physical network card remains unchanged, so the ISP will still see that MAC. They could then sell those data or give them to governments that request them!The…

Why didn’t the moderator object to sudo macchanger -r (random), but in this post that uses random with OpenSSL they’re so bothered?

mac=$(openssl rand -hex 6 | sed 's/\(..\)/\1:/g; s/.$//')

It will generate a random MAC that will hide the MAC and achieve the goal of avoid leaking your real MAC! It’s not ideal, but it’s a setup!

Isn’t it the same as:

macchanger -r <your-mac>

Aren’t they the same thing?

Why, in the other macchanger post on sys-net, they didn’t get on the author’s case for using macchanger -r to hide the MAC, but in this current post using random mac can’t?

Who invented macchanger, then, shouldn’t they have included the -r (random) option in it? Does this such famous software now have a “mortal” error?

If using a random MAC on sys-net is a problem, why did they allow that post?

Mod edit: comments on technical correctness moderation moved to its own thread:

Technical Correctness Moderation

Opening a topic to discuss technical correctness moderation. Continuing the discussion from Sys-net: random MAC spoofing and random hostname (optional) automated on every boot without installing anything:

(Technical correctness comments prior to post splitting)

Using macchanger for MAC‑spoofing on a sys‑net VM to prevent ISPs from collecting metadata that could be sold or handed over to governments

And why did the moderators allow this current post with the OpenSSL version?

Some moderators on this forum should go away. The good moderators should evaluate this.

If a post is bad and wrong, why do they approve it?

And why a post that teaches how to do the same thing isn’t said anything (case of macchanger -r), but in another one using OpenSSL to generate random MAC they get criticized for it, and it’s considered a maximum security flaw not to use a MAC with OUI?

Is this harassing the guy for no reason at all?

Just delete both posts if it’s wrong!

I agree that for greater camouflage, it’s better to always use the manufacturer MAC with OUI and never use random MAC! We shouldn’t even use random MACs; virtual machines should all have MACs with OUI, but they don’t! Whonix (desktop version, not qubes) generates random MACs and not manufacturer ones, but I think it should have OUI (independent if is in NAT internal network). However, it protects the real MAC and that’s already a defense, even if it’s not ideal!

Using random MAC also projects the leak!

The big problem is: with a post using a random MAC on sys-net, nobody says anything, but here everyone condemns the author for not using OUI?

The good moderators of this forum should organize and prevent these inconsistencies! Nobody will want to post and help on this forum anymore!