Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "virt-manager"
-
my new rig is more and more causing me issues:
- Ryzens fucking kill 9x and MS-DOS applications and the OSes themselves when they run unemulated, so they can't be run in a KVM. This makes them slow as shit, and in qemu-TCG's case, buggy as shit too. VMs can't reboot successfully, they have to be totally forced down and brought back up on TCG or they hang during the reboot. It also performs poorly. VERY poorly. The "shit runs full-speed like 65% of the time and it feels slow as fuck as video output is a stuttery blurry mess" type. This makes 2 projects problematic to complete and I have to remake 17 VMs in virt-manager now as vbox doesn't work with any virtualization method for a 9x/DOS guest now!
- For some reason my new RX 5500xt has an issue when it hits about 80% usage, the fans spin to 100% on it at 80% and taper off to like 5% when idle. Pretty standard stuff... except it's erroneously tied to... current load, not temperature. Hmm.
- Debian got an update that renames my ethernet device mid-boot. Up until just before the login screen, it's named "eth0". After that, it's named "enp8s0". This was hell to work around and idk why it does this.4 -
So just now I had to focus on a VM running in virt-manager.. common stuff, yeah. It uses a click of le mouse button to focus in, and Ctrl-Alt-L to release focus. Once focused, the VM is all there is. So focus, unfocus, important!
Except Mate also uses Ctrl-L to lock the screen. Now I actually don't know the password to my laptop. Autologin in lightdm and my management host can access both my account and the root account (while my other laptop uses fingerprint authentication to log in, but this one doesn't have it). Conveniently my laptop can also access the management host, provided a key from my password manager.. it makes more sense when you have a lot of laptops, servers and other such nuggets around. The workstations enter a centralized environment and have access to everything else on the network from there.
Point is, I don't know my password and currently this laptop is the only nugget that can actually get this password out of the password store.. but it was locked. You motherfucker for a lock screen! I ain't gonna restart lightdm, make it autologin again and lose all my work! No no no, we can do better. So I took my phone which can also access the management host, logged in as root on my laptop and just killed mate-screensaver instead. I knew that it was just an overlay after all, providing little "real" security. And I got back in!
Now this shows an important security problem. Lock screens obviously have it.. crash the lock screen somehow, you're in. Because behind that (quite literally) is your account, still logged in. Display managers have it too to some extent, since they run as root and can do autologin because root can switch user to anyone else on the system without authentication. You're not elevating privileges by logging in, you're actually dropping them. Just something to think about.. where are we just adding cosmetic layers and where are we actually solving security problems? But hey, at least it helped this time. Just kill the overlay and bingo bango, we're in!2
