It's not just protection against security, but also human error.
https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/issues/123
https://hackaday.com/2024/01/20/how-a-steam-bug-once-deleted-all-of-someones-user-data/
Just because I trust someone to write a program in a modern language they are familier in, doesn't mean I trust them to write an install script in bash, especially given how many footguns bash has.
Firstly, you may also be interested in: https://containerssh.io/v0.5/
This is a similar software, but maintained. However, it doesn't look like you limit networking with the Docker backend, beyond a simple on/off.
An even simpler solution, is to have the the ssh entry command not be the usual shell command (/bin/bash), but rather a command that starts a shell within a container. So something like:
podman run -it --rm -v "-v /HOST-DIR:/CONTAINER-DIR" docker.io/library/debian:bookworm bash would create a shell inside a short lived debian container (that is deleted upon disconnect) where a host directory is mounted inside the container.
As for mysecureshell, I would assume that since it is in the Ubuntu repos, it is still being maintained. But it's possible, since it is unmaintained that there are unknown security vulnerabilities or other issues, but:
It’ll just be for half a dozen friends for when I want to give them larger files, or if I want them to send me full-resolution photos.
If it's just for your friends, it may be okay to use a less secure solution if you trust them.
As an alternate solution: since you are looking for some sort of file searching, perhaps you could host an app explicitly designed for that, like Seafile or Nextcloud.
Also switched here. OBS on wayland has some new features, that I'm excited to take advantage of, but I still cannot find a way to share some windows, but not an entire monitor.
OBS has another feature: "virtual monitor". It does what it sounds like, and creates a virtual monitor, which you can then treat like a real monitor, like extending to, or unifying outputs, etc.
It also has a feature to share the entire workspace, but it doesn't work like I expect, and instead uses all monitors (not workspaces) as a single input source. I suspect that's a bug tbh, because this behavior is useless considering you can just add monitors as a source side by side.
I remember this being brought up with an acquaintance, but basically there's a bug where the newest fedora kernel isn't compatible with VMWare.
So yeah. Either wait for a kernel patch, or wait for VMWare to fix their stuff. But they might not, other users have mentioned that they've gone downhill after being bought by Broadcom.
If you want 3d acceleration on virtualized Linux guests, other than vmware, you have two options:
The latter is basically only going to work on a Linux host, virtualizing Linux guests (although it is possible on windows, with caveats).
The other downside is that no matter which option you pick, it's all going to end up being a bit more tinkering (either a little — assign a vm a gpu, or a lot, install unsigned windows drivers), compared to VMWare's "just works"/one click 3d acceleration setup.
No. Windows will only replace the removable media path at \EFI\boot\bootx64.efi, of the bootloader. If grub is stored somewhere else, windows won't replace it.
https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path
However, not every motherboard is compliant with the UEFI spec, and supports booting from other EFI binaries than \EFI\boot\bootx64.efi. My motherboard was one such board, where I had to force grub to install to the removable media path (which isn't the default on debian, although it is the default on a lot of other distros).
@Quills@sh.itjust.works , you should test if your motherboard properly implements the UEFI specification, by going into the UEFI menu, and selecting a different file to boot from, or changing defaults. If you look and there is no such option, or the option is ignored, then you know your motherboard isn't properly implementing the UEFI spec.
You can test if your motherboard supports booting from a different file by downloading an abitrary efi file (like memtest), and then placing it in the EFI system partition, at somewhere other than the removable media path. If you can get the UEFI to boot from somewhere other than that, then the UEFI spec is properly implemented, and Windows updates won't overwrite grub.
Of course, a simpler way to test is to simply install debian and see if it boots. If it does, then windows won't overwrite grub. If not then it will. You can then install a different distro from there.
Wezterm. I started out on konsole, and was happy with it, but then I started using zellij as my terminal multiplexer. Although zellij allows you to configure what command copies and pastes text, copy/paste on wayland and windows only works by default with wezterm. It gives me consistency across multiple DEs/OSes, with minimal configuration, which is good because I was setting up development environments for many people, with many configurations
schadnefreudne
This one is good, but I read right through it — although reading out loud would probably make this more difficult, it really depends on the streamers familiarity with the words. Possibly they might be tripped up, and possibly they would struggle.
This does give me an idea to use words which are hard to pronounce, like gif (which is actually pretty easy, just use the G in GiGantic). And then force them to pronounce them, or argue about pronunciation.
I switched to Incus for my homelab.
Blogpost: https://moonpiedumplings.github.io/projects/build-server-6/