DefederateLemmyMl @ SpaceCadet @feddit.nl

* Gen𝕏

---

Read more

Posts

1

Comments

584

Joined

2 yr. ago

Multilib packages aren't installed by default just by enabling the multilib repo, so yes you need to find the lib32 libraries your application needs and install them by hand.

Perhaps it's a 32-bit application and it needs lib32-zlib.

What does ldd ./runner say?

in early 2000’s, internet access was extremely fucking expensive, so most software was peer-to-peer shared, not even by torrent, but on CD’s or floppys, or local neighborhood ad-hoc and internal ISP networks

Uh no. I was there. In 1995 or 1996, I may have still used a shareware CD-ROM, or some less-legal compilation CD-ROM, but in the 2000s the most common way to install software by far was to download it over the internet.

And there was no access control whatsoever. A literal spyware with full access to your system, that only puts a purple fucking gorilla on your screen, that runs around and does absolutely fucking nothing? Sign me the fuck in. If your virus did something even something remotely useful, like show weather and currency rates, then you could rest assured that it would infect every single computer in the country.

I think the point of the post is that back then people were warned against installing bonzi buddy and such, and we were told to install software only from trustworthy sources. Spyware software rightfully flagged such software as malware too. Nowadays, there are appstores full of banal apps which harvest much more personal information about you than bonzi buddy ever did and we're not batting an eye about it, and even though we have "Access control" we just happily click accept when our calculator wants to read our emails, and we've accepted it as a normal way of doing things.

But everyone says its always breaking and gives problems. That’s because of users, not OS… right?

It's an exaggeration, it doesn't always break but yes it occasionally does. Any Arch user who tells you otherwise is lying or hasn't used Arch for very long yet.

That’s because of users, not OS… right?

No it's because of regressions in new releases. Arch relentlessly marches forward and always tries to give you the latest-and-greatest version of any package on your system. There is some testing done obviously, but it can never be ruled out that newer software contains new bugs and regressions that are not caught in testing, and that it ends up being released.

To give an example of such a regression, the past few weeks there have been some kernel releases with broken bluetooth support for the (very common) Intel AX200 chipset. It is fixed now, but if you wanted to use bluetooth, Arch was in fact broken for some time.

The fix is usually: temporarily rollback the offending packages until the issue is fixed upstream or until a workaround is found. It does mean you will occasionally have to spend some time diagnosing issues and checking user forums to see if other users are having the same problem.

There was a short period of time when enlightenment was the default window manager for Gnome, later to be replaced by Sawfish. It was a hideous experience by the way.

Early Gnome was weird. The Gnome File Manager was also originally based on the terminal program Midnight Commander.

Good news ... it's a suppository!

videos above 1080p can sometimes cause problems if they have heavy encoding like vp9 or av1

Yeah they're probably decoded in software because I doubt that the integrated graphics supports hardware decoding of those recentish codecs.

At that point, just put a gt1030 in it.

Actually, are these 2 forks of another, when?

Yes forgejo was forked from gitea in 2022. It was a soft fork at first, but became a hard fork earlier this year.

Full story here: https://forgejo.org/2024-02-forking-forward/

True that. Hadn't thought of that as it's not my typical VPN use case.

I'm not sure what a VPN provider could do about that though, they don't control the operating system's networking stack. If the user or an outside process that the user decides to trust (i.e. a dhcp server) adds its own network routes, the OS will follow it and route traffic outside of the tunnel.

The defenses I see against it are:

• Run the VPN and everything that needs to go through the VPN in a virtualized, non-bridged environment so it's unaffected by the routing table.
• Put a NAT-ing device in between your computer and the network you want to use
• Modify the DHCP client so that option 121 is rejected

Edit: thinking about it some more, on Linux at least the VPN client could add some iptables rules that block traffic going through any other interface than the tunnel device (i.e. if it's not through tun0 or wg0, drop it). Network routes can't bypass iptables rules, so that should work. It will have the side effect that the VPN connection will appear not to work if someone is using the option 121 trick though, but at least you would know something funny was happening.

Don't you control your dhcp server?

It was a bit rocky coming over from Plasma 5, but settled in nicely now.

Oh and don’t forget to take backups of your /home. Thats good practice for every desktop environment.

The config files of the major desktop environments have become a mess though. Plasma absolutely shits files all over ~/.config and /.local/share where they sit mingled together with the config files of all your other applications and most of it is thoroughly undocumented. I've been in the situation where I wanted to restore a previous state of my Plasma desktop from my backups or just start with a clean default desktop and there is just no straightforward way to do that, short of nuking all your configurations.

Doing a quick find query in my current home directory, there are 57 directories and 79 config files that have either plasma or kde in the name, and that doesn't even include all the /.config/* files belonging to plasma or kde components that don't have it in their name explicitly (e.g. dolphinrc, katerc, kwinrc, powerdevilrc, bluedevilglobalrc , ...)

It was much simpler in the old days when you just had something like a ~/.fvwmrc file that was easy to backup and restore, even early kde used to store everything together in a ~/.kde directory.

apt purge nano is one of the first things I do on a new Debian installation. Much easier to remember than having to use update-alternatives, select-editor and the $EDITOR variable to convince the likes of vigr,vipw, visudo,crontab -e,... that I really want to use vim as my primary editor.

Not really, because you're now going to make it do more, i.e. incorporate the functionality of sudo and expose it to user input. So unless you can prove that the newly written code is somehow inherently more secure than sudo's existing code, the attack surface is exactly the same.

The attack surface will be a systemd daemon running with UID=0 instead, because how else are you going to hand out root privileges?

So it doesn't really change anything to the attack surface, it just moves it to a different location.

I wonder if it’s possible to run their remapping program in a Windows virtual machine.

That should work if you can pass through the entire USB host device to the VM.

I do this with my QK80, which also has Windows only software. I have a KVM virtual machine with Windows, and when I want to configure the QK80, I use the "pass through USB host device" option to give it direct access to the keyboard, and run the software in the VM. It works fine.

If you do this, you temporarily need to connect a second keyboard though because as soon as you pass through the keyboard to the VM it becomes inaccessible for the host OS.

We are talking about LTS distros, not about bridges. The context is pretty clear.

That's a you problem. Your interpretation is wrong.

Quoting from the Debian Manual:

This is what Debian's Stable name means: that, once released, the operating system remains relatively unchanging over time.

Stable means unchanging in this context.

Just go Debian.

Ubuntu used to bring a bit of spit and polish at a time when most Linux distros lacked that. Nowadays it brings nothing worthwhile to the table anymore, it's just brand recognition, but what it does bring is aggravation for experienced users.

I had this realization a few years ago when I found myself fighting against 20.04 and I asked myself: what exactly is Ubuntu doing for me that plain Debian can't? The answer was nothing really, so I moved all my Ubuntu VMs over to Debian Bullseye and never looked back.