Well, from non-LTS, you can always go to +1, the next release. If this happens to be an LTS, sure, you will automatically be on LTS. (Then you can change your settings to say on LTS or keep tracking non-LTS release).

That’s what I was thinking. And, they don’t really give any reason why their design is better.

If it works for you then use it, however if you want the latest packages you’ll have to NOT use the LTS releases in which case be prepared to do a FULL REINSTALL every time a new version comes out.

This is just wrong. You can update the LTS release to the next non-LTS release. You only have to unchecked “LTS only”. You can also wait for the next LTS release.

You never need a full install. I haven’t done such a thing for a decade.

Well, I’d file this as innovation. Innovation is trying and failing. It’s an experiment. And I’m okay with this.

Is it wasteful to have KDE and Gnome? Why don’t they give up and merge with each other? Did we really need systemd? Or docker? And why Wayland when every single distro is on X and every single application is on X?

Ubuntu started as a Gnome-based distribution and it is was better than the competition on the desktop at the time. Or good enough. It got popular.

Personally, I wasn’t a big fan of Unity or Gnome 3, but it worked. I found snap totally weird and against how things should be on a Linux system. But snap updates (while still annoying) have solved problems with deb-based updates of browser (“Quit all running firefox or you’ll experience problems”).

Maybe I’d like Debian more. After all I came from Debian to Ubuntu. But it’s not worth to make a fuzz.

That’s a good threat if plausible.

That’s probably not a good plan, however. What you gonna do after the blowing up the plant? Emigrate, maybe, but for those who’ll stay: Congratulations, you have just blown up your job, your life and any bargaining chip you ever had.

Aren’t they negoting with Hamas? They probably know where they are…

Austerity, well. They want subsidies on Diesel.

Ubuntu is nice. Apt/DEB works as they should. Some default apps, mostly browsers, are snaps now, but this does not bother you at all. You were getting them from your distro anyway.

Flatpak and AppImages work just fine if you need them.

The Ubuntu desktop (any flavour) just works. Others are different, but nothing is bad about Ubuntu.

Ubuntu is trying new things, proprietary to their ecosystem, e.g. Unity or snap. On the big picture, those are experiment. Ubuntu is still Linux.

The community reaction to snap is overblown. So Canonical developed something you don’t like? Ignore it. This has mostly been a waste of time for them.

(Yes, maybe that dev time would be better spent on flatpak or open-source apps. But that’s their time. I’m not paying Ubuntu developers, so can I really complain?)

We’re an extremely versatile, mobile species, even to the point of being capably semi-aquatic sometimes.

And here am I, hardly capable of leaving my chair.

Of course, it’s not an actual highway, but the myth was there’s no (safe) way for humans to cross the gap (over land). And now people just do it.

The “Darian gap” not a gap anymore?

Sane people will continue to wear the mask in crowded places.

mobility

= automotive = fossil fuels

“Tja” as we say in German.

So many Russians on permanent vacation / early retirement / digital nomand lives in five days.

Well, not an expert. We learned now that logos are not signed. I’m not sure the boot menu config file is not either. So on a typical linux setup you can inject a command there.

True, but this was the case without this finding, wasn’t it? With write access to the EFI you could replace the boot loader and do whatever you please.

Yes, that’s my understanding. A normal user cannot do this. (And of course, an attacker shouldn’t not control a local user in the first place.)

Physical access is also a risk, but physical access trumps everything.

This is also my understanding, at least of you keep the EFI partition.

There are several ways to exploit LogoFAIL. Remote attacks work by first exploiting an unpatched vulnerability in a browser, media player, or other app and using the administrative control gained to replace the legitimate logo image processed early in the boot process with an identical-looking one that exploits a parser flaw. The other way is to gain brief access to a vulnerable device while it’s unlocked and replace the legitimate image file with a malicious one.

In short, the adversary requires elevated access to replace a file on the EFI partition. In this case, you should consider the machine compromised with or without this flaw.

You weren’t hoping that Secure Boot saves your ass, were you?

Summary does not contain the actual vulnerability or exploit.