RAM was increased from 768 MB RAM to 1024 MB RAM for Whonix-Workstation. For now it is temporary, but it may also be permanently depending on near time developments. Discussion ongoing. Please contribute if you can share ideas or code on how to reduce RAM usage.
Everything is good and connection works flawlessly. anon-cnnection wizard looks sexy. Thanks @iry!
whonixcheck on GW complains that QEMU is unsupported although its KVM. So users might be needlessly alarmed.
ERROR: Virtualizer qemu unsupported by Whonix developers! Whonixcheck aborted! (qubes_detected: false)
Using Virtualizer qemu together with Whonix is recommended against, because it is rarely tested. [1] [2] [3]
It could be made possible, but would require more Whonix contributors.
It may already work, but is highly experimental.
This might endanger your anonymity. Do not proceed unless you know what you are doing.
If you wish to ignore this warning and to continue whonixcheck anyway, you can set
WHONIXCHECK_NO_EXIT_ON_UNSUPPORTED_VIRTUALIZER="1"
in /etc/whonix.d/30_whonixcheck_default.conf.
Recommended action:
Shut down.
Read Whonix documentation [4].
Use Whonix with a supported virtualizer or Physical Isolation [5].
Shared folders seems to be broken. While a folder named after the mount point is visible, nothing from the host shows up in it. It could be that I’m not familiar with a new path that it was changed to when the feature was revamped by Jason
When talking to Debian servers apt fetches from onions and clearnet. Seems redundant. Is this the correct behavior or did you forget to remove clearnet repo links?
Thanks for the update on the GW after running sudo apt-update && sudo apt-get dist-upgrade - and rebooting I get a message No command arguments supplied! Usage: kdesudo [-u ] KdeSudo will now exit…
Just ran a new instance of the WS same message
I have only run the update - using the testers repo and changed passwords?
It’s about auto starting anon-connection-wizard. Or not. So in worst case a usability bug. No security involved.
Not clear how that could happen. We checked all the related code and added some safeguards against this which will end up in updates and the next release.
Shared folders seems to be broken. While a folder named after the mount point is visible, nothing from the host shows up in it. It could be that I’m not familiar with a new path that it was changed to when the feature was revamped by Jason
No changes where done.
Is package shared-folder-help installed?
/lib/systemd/system/mnt-shared-vbox.service was removed since no longer
needed. Unrelated to KVM.
/lib/systemd/system/mnt-shared-kvm.service is untouched.