SimpleX setup with dispvm

[rzg]

Yes, as mentioned here:

Send Telegram Messages over Tor with Whonix ™

But I think we could circunvent it using bwrap rules,

• Unix Time-sharing System Namespace: --unshare-uts option when invoking bwrap.
• Custom Hostname: --setenv

For example

bwrap --unshare-uts --setenv HOSTNAME "custom"

I did little test, this also makes Telegram display: “XEN”.

I think a Linux guru who understands namespaces could help us create a fake system using bwrap.

Xen-specific system files:

/sys/hypervisor/uuid

/proc/xen

/dev/xen

/proc/cpuinfo

Like:

  --bind /tmp/fake-proc/cpuinfo /proc/cpuinfo 

Maybe we could consider other sandbox solutions, like Podman

I found these interesting references:

Stop telling VMs the exact physical CPU model in the computer

Waydroid template

This is old, but talks about other possible problems with xen changing the CPUID: https://xenbits.xen.org/people/andrewcoop/2016-Summit/cpuidlevel.pdf I didn’t fully read your thread, but wanted to make sure that you know that the instructions ( xl.cfg - xl domain configuration file syntax ) say that you can add “cpuid=” to /etc/libvirt/libxl/{qube name}.cfg /etc/libvirt/libxl/{qube name}.cfg is auto-generated, so you would probably want to change the template (which i believe is /usr/share…

Waydroid template

Waydroid seems to be the only option for android simulation besides “native” x86 android, because inside a Qubes-VM one can only use “containers” (Linux kernel does not have containers!), meaning namespaces and some enforcements like cgroups, selinux. Experiments? My tests with https://www.genymotion.com/ showed that they require the virtualization features to be present in the CPU, but unfortunately evil XEN already ate all the nice HW-virtualization so genymotion can not run its Fake-ARM …

Waydroid template

you guys are over complicating it. all you need to do to hide cpuid from an app in waydroid is chmod 440 /proc/cpuinfo before starting waydroid this could probably be implemented in a systemd thing at start up but that’s for someone else to do i don’t find it very important

Browser fingerprinting on qubes

I was looking for the same and managed to fix it like this: Hostname Configuration Method for App VM To modify the hostname in an application virtual machine (appvm), you can use the following approach: Open the /rw/config/rc.local configuration file Add the command: hostnamectl hostname [new-hostname] Example: hostnamectl hostname mystery-machine To check the result restart the AppVM and run hostnamectl in the commandline. Additional configuration options include: Changing the icon nam…

Making a stealthy windows qube?

This is not going to be easy, considering that one would need to hide its presence from several low and high level tricks, rather than only from human eye. Some food for thought: GitHub - a0rtega/pafish: Pafish is a testing tool that uses different techniques to detect virtual machines and malware analysis environments in the same way that malware families do And related entries, e.g. from the most recent issue in that repository: How anti-cheats detect system emulation | secret club

A little off topic, but worth to mention:

GitHub - segofensiva/OSfooler-ng: OSfooler-ng prevents remote active/passive OS...

“…to camouflage and modify in real time the flags in TCP/IP packets that discover your system.”