It’s a usability issue: confusing message.
This should help.
Upon reflection, the security impact of this seems far greater than anything related to hardware identifiers.
Therefore this feature shouldn’t be dubbed as Restrict Hardware Information to Root but Reduce Kernel Information Leaks?
I could rename the systemd unit and keep an systemd Alias= for legacy compatibility.
Due to today’s discussion on telegram, I’ve just now updated the documentation of this feature to clarify what it can do and what it cannot do.
security-misc: Enhance Miscellaneous Security Settings
Yes, that’d be a good idea.
1 Like
Is this recommended for increase anonymity? i see that it breaks applications that why I’m 50 50 on it. Should the risk he taken for the anonymity (want as much anonymity as possible)
Using: Qubes-whinox
That is already documented here:
This link has been notorious for not working for me. I checked out the GitHub for it though. All it says is what I have already said. I’m asking if whinox is still usable in particular qubes-whinox with it install, I don’t see any feedback on what exactly it breaks and if it’s worth it even with its security benefits to have it install, all I have seen is bug fixes from users.
It’s testers-only.
Good afternoon.
I would like to hide the kernel version and CPU model from applications using security-misc. When I activate “sudo systemctl enable hide-hardware-info.service” and after further reboot, the system turns on, but other than mouse movements, I can’t do anything else with it. It does not react to anything, even to the commands ctrl+alt+delete and ctrl+alt+f1-12, the exception - the button to shut down the virtual machine.
Experimentally found that if you add user to group sysfs through the command “sudo addgroup user sysfs” - the system is fully operational and even hidden CPU characteristics from applications. But the kernel version information still escapes to the public, strangely enough.
How can I make the kernel information to be hidden at least from third party applications? I should point out right away that I am far from IT and how linux operating system works.
I tried running the systemd service as a sysfs group by creating a drop-in directory, but it didn’t work. Probably because I did it wrong. I created the directory “systemd.d” in the folder “etc” and added files called “sysfs.conf” and “50_user.conf” with the contents of “[Service]
SupplementaryGroups=sysfs”, it had no effect. Also in the /etc/systemd/ directory I added all the same content to the “system.conf” and “user.conf” files, and the result was the same. Adding new files “sysfs.conf” and “50_user.conf” to this same directory also failed.
I should add that these problems equally apply to whonix 16.0.3.7 on kvm and version 16.0.4.2 on virtualbox.
In turn, security-misc, installed on a clean debian 11.3.0 xfce image on kvm showed full functionality from the first time without any tinkering.
working fine (tested in qubes) except it all add additional boot delay
1 Like
This needs some documentation how to test this:
https://www.kicksecure.com/wiki/Security-misc#Testing
1 Like
Now documented.
I was able to fake CPUID on VirtualBox using vboxmanage. Then I found ⚓ T408 --synthcpu was removed from VirtualBox, use --cpuid-portability-level or --cpuidremoveall?
Anyway, for the record:
set vm=“Whonix-Gateway-XFCE”
vboxmanage modifyvm %vm% --paravirtprovider none
vboxmanage modifyvm %vm% --cpuidremoveall
vboxmanage modifyvm %vm% --cpu-profile “Intel Core i7-5600U”
Breaks flatpak.
flatpak run org.chromium.Chromium
bwrap: Can’t find source path /sys/block: Permission denied
I don’t see a lot spoofing there. It might make you stand out more unless you could come up with a way to spoof more information.
Never mind “cat /proc/cpuinfo” for now. See: /proc/cpuinfo versus cpuid (written just now).
Instead, try using cpuid (which gets the information directly from the CPU):
cpuid usage
Then compare using CPUID Spoofing Testing (written just now).
1 Like
I don’t see a lot spoofing there. It might make you stand out more unless you could come up with a way to spoof more information.
I can certainly do some more spoofing, like reporting a Pentium D. But it’s pointless, you don’t need CPUID to detect some features.
You mean that all CPU spoofing attempts are currently futile? I’d agree.
1 Like
