That’s a problem many LTS distro users don’t seem to understand when they first install their distro of choice: the LTS guarantees only apply to the software made by the distro maintainers.
Loads of tools (GUI or command line) used in development normally come from external repositories because people deem the ones in the upstream repos “too old” (which is kind of the whole point of LTS distros, of course).
You can still run 16.04/18.04/20.04 today, but you’ll be stuck with the software that was available back when these versions were released. The LTS versions of Ubuntu are great for postponing updates until the necessary bug fixes have been applied (say, a year after release) but staying more than one full LTS release behind is something I would only consider doing on servers.
For sure, I’m on the latest LTS! The problem here is that the remote ssh tools don’t work on older servers either, so you can no longer use the same workflow you had yesterday if you’re trying to connect to an 18.04 Ubuntu server
I never really trusted their “sftp a binary to a server and launch it” approach of server-side development, but this really shows how frail that approach can be. Sounds like an excellent time to look for alternatives, in my opinion.
Perhaps VSCodium will be able to get remote development working again? If there’s an open source version available, that is. I think there’s an unofficial addon?
They announced dropping the old glibc version half a year ago, so I doubt that’s the reason. Besides, most LTS releases backport security fixes like these to old versions, so there’s no reason to assume an old version number is vulnerable necessarily.
That’s a problem many LTS distro users don’t seem to understand when they first install their distro of choice: the LTS guarantees only apply to the software made by the distro maintainers.
Loads of tools (GUI or command line) used in development normally come from external repositories because people deem the ones in the upstream repos “too old” (which is kind of the whole point of LTS distros, of course).
You can still run 16.04/18.04/20.04 today, but you’ll be stuck with the software that was available back when these versions were released. The LTS versions of Ubuntu are great for postponing updates until the necessary bug fixes have been applied (say, a year after release) but staying more than one full LTS release behind is something I would only consider doing on servers.
For sure, I’m on the latest LTS! The problem here is that the remote ssh tools don’t work on older servers either, so you can no longer use the same workflow you had yesterday if you’re trying to connect to an 18.04 Ubuntu server
Very strange, it seems like they have raised their minimum glibc version, but I can’t really tell why. Based on the announcement on dropping VS Code server support for older distros posted last August I think it has something to do with NodeJS, so I’m guessing it’s because their server-side binary is written in NodeJS as well?
I never really trusted their “sftp a binary to a server and launch it” approach of server-side development, but this really shows how frail that approach can be. Sounds like an excellent time to look for alternatives, in my opinion.
Perhaps VSCodium will be able to get remote development working again? If there’s an open source version available, that is. I think there’s an unofficial addon?
Maybe because of the privilege escalation that was just found in glibc?
https://www.bleepingcomputer.com/news/security/new-linux-glibc-flaw-lets-attackers-get-root-on-major-distros/
They announced dropping the old glibc version half a year ago, so I doubt that’s the reason. Besides, most LTS releases backport security fixes like these to old versions, so there’s no reason to assume an old version number is vulnerable necessarily.
Yeah. Fuck stable dev platforms, amirite?
You can cure yourself of that shiny-things addiction, but you have to go attend the meetings yourself.