by disintegrator on 12/29/24, 5:51 PM with 143 comments
by cranium on 1/2/25, 4:28 PM
After failing to install Windows in a VM (thanks TPM), I found a way to run Windows apps nearly natively (https://github.com/winapps-org/winapps). It works by starting a Windows docker image and streaming the application frame with RDP. As the RDP client handles the copy/paste and other niceties such as shared directories, it's way easier to integrate in my env than the other options.
by nneonneo on 1/1/25, 11:58 PM
My specific setup is that I use an authorized_keys entry on the host that restricts the guest to running a specific command, which limits what a compromised guest can do to the host. The command is set to a script that has a list of specific permitted actions. This is a good option if you’re looking for a bit of additional isolation between host and guest.
by apt-apt-apt-apt on 1/2/25, 2:32 AM
When it successfully installed, it was terrifying to think that all source code, private files were instantly shared with malicious actors. Not only that, there was the prospect of having to somehow wipe and ensure all files were clean, reinstall the OS, and the possibility of some bootloader remnant still lurking.
In this case, it seems that a security package had replaced a previous malicious package, making this instance benign. But it feels like I am only one typo away from an absolute catastrophe every time I install a package.
VM seems like a good way to add some protection.
by Abishek_Muthian on 1/2/25, 8:49 AM
After a 5 years hiatus I started developing mobile apps again and I was frustrated to learn that Apple doesn't allow renewing the developer license on web anymore, I don't own a Mac and even Apple developer app on iPhone didn't allow me to renew my license.
After I signed into a macOS VM, I was able to renew my license through Apple Developer App on iPhone as macOS version of the app requires T2 chip.
Now I have PTSD flashbacks of why I left mobile development in first place.
by TowerTall on 1/2/25, 6:39 AM
by moritonal on 1/1/25, 10:07 PM
by mongol on 1/1/25, 10:23 PM
by disintegrator on 1/2/25, 12:51 AM
Now I know what all the WSL users experience seamlessly with their setups. Glad I have something that comes close.
by mmwelt on 1/2/25, 2:26 AM
by crabbone on 1/2/25, 9:42 PM
The only kind of plausible explanation the author gives is that it's "more secure" because the imaginary attacker will have to take an extra step to get the password from the VM instead of the host OS? -- This seems like such an inconsequential / worthless benefit to jump through the hoops of running things in a VM...
Like... I wasn't sold on this approach from the get go, and this pitch makes it sound like I was right all along?
Other non-starter "bonuses" include not installing developer tools on your laptop that you have for... drum roll... development. Why? It's sole purpose is to be used for development, why not install development tools on it? Just doesn't make any sense...
by zokier on 1/2/25, 6:34 AM
It is especially nice in corporate environment, where the host system is generally managed by IT and the devices are largely impersonal (standardized configuration, standardized software). You can carve out a corner to make your own and work there. <insert rant on ineffective corporate IT>
by gbraad on 1/2/25, 5:04 PM
by tkiolp4 on 1/1/25, 11:06 PM
Don’t understand the need for Tailscale either. When I’m running services or dbs inside the VM, I can easily access them if needed from the host (either by IP or by the hostname I gave to the VM on start up)
by lizknope on 1/2/25, 12:57 PM
> My physical machine is a 2023 MacBook Pro with M2 Pro CPU
> I’m using VMWare Fusion Pro
> Quite often I’ve found developers frowning up Ubuntu and preaching for folks to use NixOS, Arch, Debian or other distros. The reality for me was Ubuntu was the fastest way to get set up and now
I'm in integrated circuit / semiconductor design. At every big company over the last 30 years we are given a computer and we can change the desktop environment but we aren't installing our own operating system.
The people I know in software have a common OS, compiler, and build environment. They aren't dictating what text editor you use but you aren't working on projects individually but together.
So if everyone at the author's company is doing their own thing do they have problems integrating all the code together? "Oh you used version 2.3.4 but I used version 2.4.7 which fixed this issue, what are we using to ship with?" Or is this not a problem?
by sushidev on 1/2/25, 7:04 AM
by raihansaputra on 1/2/25, 2:10 AM
by mrbluecoat on 1/1/25, 10:42 PM
by tonymet on 1/2/25, 1:09 AM
by Too on 1/2/25, 12:19 PM
by arkh on 1/2/25, 8:02 AM
My setup is mostly one VM per project group / online identity. Most of them using Ubuntu. The problem is when I want to work on an old project to check how it likes new technology I tend to stumble into the "you should have kept the OS up to date" problem. Ubuntu does not make it easy to upgrade if you miss more than a year of update.
And even if you keep up to date, they tend to break things often (loved the X11 to weyland switch when working with screen capture libraries) so new VMs are using debian.
by nkko on 1/3/25, 4:33 PM
Disclosure: I work on this project
by dsfsaff on 1/1/25, 10:29 PM
by jareklupinski on 1/1/25, 10:12 PM
maintaining consistent firmware development environments using containers is a great idea, and current solutions involving proxying the compiled binary work well for flashing quickly, but switching back and forth between UART and Serial Debug is always more convenient when the IDE can handle it all
by pjmlp on 1/2/25, 8:02 PM
Likewise when Windows 7 came out, I stop bothering with dual booting hassles and using VMare Workstation instead for whatever Linux.
The exception being a netbook from the Asus Linux netbooks glory days, a price category nowadays replaced by tablets.
by amelius on 1/1/25, 10:13 PM
by rcarmo on 1/2/25, 9:42 AM
by secondcoming on 1/2/25, 1:30 PM
by mootoday on 1/2/25, 9:27 AM
Happy to set it up and demo if you can share (or DM) a repo URL.
by firesteelrain on 1/2/25, 12:00 AM
We reach our VMs via VDI.
by pshirshov on 1/2/25, 11:02 AM
by urronglol on 1/2/25, 1:20 PM
by hrtk on 1/2/25, 4:11 AM
by TacticalCoder on 1/2/25, 12:30 PM
Such a setup works (I'd know for I have one at home doing just that but it's not my main PC) but how's it like to work like that?
The GPU hooked to the hypervisor can either be on another monitor or on another input (in the latter case you'd "go" to the hypervisor by changing the monitor's input).
by tonymet on 1/2/25, 2:16 AM