I wouldn't recommend virtualbox on linux these days. It's slower than kvm, and oracle is known to send hefty bills to companies when their employees install virtualbox's proprietary extension pack on their machine.
redcalcium
joined 2 years ago
Assuming you're on desktop, just grab a cheap amd gpu and do the gpu passthrough setup with kvm and virt-manager. No need to get an expensive gpu if you don't plan to play games on the vm. The cheapest, bargain-bin second hand gpu will do, as long as it's not too old.
This proves that ps portal is actually could be a capable handheld. Shame, it probably got enough processing power to run vita games. It has an adreno 610 gpu, which is much more powerful than vita's gpu.
In that case, perhaps replacing -o sftp_server="/usr/bin/sudo /usr/lib/openssh/sftp-server" with -o sftp_server="/usr/bin/sudo -u <syncthing_user> /usr/lib/openssh/sftp-server" is a good compromise?
They turn a blind eye as long as no one files DMCA notice. They do limit downloads of some popular pirated materials behind login though.
So the workaround is running the SFTP process as root?
Why not run the SFTP server as a docker container as well (e.g. with https://hub.docker.com/r/atmoz/sftp/ )? You can mount the same volume in the SFTP container, and have it listen on some random port. Just make sure to configure the SFTP container to use the same uid:gid as the one used in the syncthing container to avoid file permission issues.
Compromised iot devices sold as residential proxy is pretty hot right now: https://thehackernews.com/2024/03/themoon-botnet-resurfaces-exploiting.html?m=1
Those are targeting Linux routers and iot devices though. However, esp32 had vulnerabilities in the past such as the fatal fury attack, though it requires physical access to execute.
The easiest setup I tried so far is to simply put your docker container's volume on an external path, e.g. /mnt/hdd1/some-directory, instead of putting it in the standard docker location (/var/lib/docker/volume). You'll have full control over ACL on those custom paths.
I think it's because how simple and ubiquitous it is. Just open the backplate and stick it to your detonator to use the speaker terminal as a source signal.
This page has more info: https://timbin.wordpress.com/2013/07/30/hacking-like-a-terrorist-the-casio-f-91w/
Some distro actually do not map www-data user to UID 33, so if you're on one of those distro, changing file owner to UID 33 won't help you. Pretty sure Ubuntu use UID 33 though, but I've seen people on other distros getting bitten by this. Also, some container systems can remap file ownership when mounting a volume.
One thing to watch for is file permissions. Just make sure it's all set to www-data and you're golden.
What kind of drama did I miss?