Removed by mod

Yes but I think the commenter is saying that if a person had installed this package, removing the package in the package manager is probably insufficient to remove the infection from the machine.

Compliant with RVA23* (excluding “V” extension)

Does this mean that it will or won’t be compatible with Ubuntu 25.10 (that is targetting RVA23)?

I’d just like to interject for a moment. What you’re referring to as Linus Torvalds, is in fact, GNU/Linus Torvalds, or as I’ve recently taken to calling it, GNU plus Linus Torvalds.

I do not want to waste everyone’s time by continuing this discussion that is not leading anywhere.

Not leading anywhere? That’s a strange perspective to have given the “overwhelmingly negative feedback.” I think it led to a fairly concrete conclusion.

I think what he meant to say was “I don’t like that my arguments did not sway your opinion.”

It’s the effect of a persistent decades-long disinformation campaign perpetrated by those who wish to destabilize western democracies which has been signal-boosted by naive (or maliciously designed) recommendation algorithms on social media platforms.

There is nothing to be “weary” of

I checked, and OP actually spelt “wary” correctly.

bash scripting is not intended to perform all of your logic in the scripting language, it’s intended to call out to other programs which perform specific tasks. The entire POSIX command set is your bash scripting language.

Your script is a simple one-liner if you know some simple commands:

$ head -n 1 /usr/share/dict/words | tee /dev/stderr | tr -d '\n' | wc -c
A
1

Yes, that’s the same thing. Removing it from one place, and just adding it to another.

Adding it where?

but maybe I’m missing something.

Yes, FTA:

May 13, 2026: the tlsclient ACME profile will no longer be available and no further certificates with the Client Authentication EKU will be issued.
…
Once this is completed, Let’s Encrypt will switch to issuing with new intermediate Certificate Authorities which also do not contain the TLS Client Authentication EKU.
…
After this change is complete, only TLS Server Authentication will be available from Let’s Encrypt.

What is the public key infrastructure for obtaining client authentication certificates that have a path of trust back to a root CA? You said separate PKI for every use case, so what is the intended PKI for this use case, if not CAs like LetsEncrypt?

This honestly is basic security in a number of ways. Separate PKI for every use-case is the standard.

So what is the PKI for client certificate authentication?

a ISO

Naming things really is that hard?