francescovv
Joined 7 years ago
Joined 7 years ago
Is it not? [st] requires exactly that. And it works for distros, from what I can tell - debian/ubuntu, arch, almost everybody seem to ship it just fine.
In fact, malice and incompetence are not necessarily mutually exclusive.
This very incident shows several instances where "Jia Tan" is being arguably incompetent, in addition to being clearly malicious: unintended breakage by adding extra space between "return" and "is_arch_extension_supported"; several redundant checks for `uname` == "Linux"; botched payload, so "test files" had to be replaced, with pretty fishy explanation; rather inefficient/slow GOT parsing, list goes on...
And for mobile phones - without internet is similar, unnecessarily hard. The other day I was hiking with friends, and wanted to share a .gpx file with the route, at some spot with no cell coverage. I thought: "I 'member, bluetooth can send files". Well, we spent good 15 minutes trying and miserably failed, that's no longer possible in the name of "security". So I had to wait for cell signal to come back and send the file via whatsapp. To someone standing right in front of me.
It might be a while till that is feasible, though. Until then, "content safeguards" will continue to feel like overreaching, artificial stonewalls scattered across otherwise kinda-consistent space.
Arch doesn't either.
In fact, official releases of openssh-portable don't. One has to patch it for that. Debian and Fedora (as well as their downstreams) do apply such a patch [1]. Most other distros don't.
[1] https://sources.debian.org/src/openssh/1%3A9.7p1-2/debian/pa...
Apologies for nit-picking, but that's not quite how sum-of-probabilities work. Total probability across 200 tries of 1% chance each, is ~87%:
p=0
for _ in range(200):
p=p+(1-p)*.01
print(p)
0.8660203251420382
Your "sooner or later, to the point where we can assume" conclusion, still stands, of course.That's [ULA], isn't it? This tech was also known as "Gate Array", before FPGA came along.
Where do you see that, sorry? I'm looking at the "Download Source Package" section here:
https://packages.debian.org/sid/stterm
...and the only patch on there is debian/patches/0001-fix-buffer-overflow-when-handling-long-composed-inpu.patch, which doesn't touch Makefie.