c0l0

It's rather uninteresting to note, once again, that Ubuntu has decided to do this. I would like to know the (official, if any - unofficial/speculative otherwise) reason WHY they have not.

It does not seem that complicated to patch, and kernel upgrades are a dime a dozen these days. So what is making them delay a fix for so long?

If you actually think it's a trivial affair to change a well-established default with more than 20 years of history that is, on top of all other difficulties that such a change typically encompasses, used to identify and name things, I hereby beg you to never design or provide any kind of infrastructure.

That's nice and all, but OpenWrt (and its use of .lan) predates this particular RFC by a rough 14 years.

I hope the gTLD application gets struck down.

As an irregular user of spice (via Proxmox PVE), I wish the stars would align for QEMU to gain support for sunlight/moonlight streaming directly in the hypervisor. That'd be a killer app for VDI-style infrastructure, now that accelerated guest graphics via Venus, VirtIO GPU, and Intel's support for SR-IOV is finally coming together.

This is loser talk.

Imagine what Debian could accomplish with that kind of money...

Heh, one of my most prized posessions in my teens was a GlobalWin FOP38 with that PAL6035 you mentioned mounted. An absolutely CRAZY fan that had no objective right to exist, much less in a teenager's Socket A Celeron rig.

I remember the day it arrived in the mail and I installed it - my family had just recently moved into a new house where my own room was located directly above the living room. When I started my PC with the new cooler and fan for the first time, the noise (esp. the obscene vibrations through the floor/ceiling!) actually prompted my mother to visit and check what's up/wrong :D

I ended up rigging together two chopping boards and a few pristine cleaning sponges as a kind of pedestal for my big tower case to rest upon, and was allowed to operate that way for the months to come. If it weren't for the over-ear headphones I wore all day back then, I guess I would have had suffered hearing loss from the noise exposure rather sooner than later...

Ouch, that poor die :(

I remember it well, back in the very early 2000s, when my own Athlon XP 1800+ (an AGOIA stepping, I do know that for sure :D) met its untimely end at the hands of a device that was designed to prevent the exact misfortune that killed its sister CPU as seen in this submission!

The fragile silicon was a problem the enthusiast/PC-builder community was very aware of, and the market responded with "spacer" kits you could buy for a few $$$ that were cut from solid sheets of thin copper. These spacers would carefully wrap around all the little bumps on the CPU's upper side, and provide a level plane for the heatsink to rest upon, while still establishing direct contact with the die that it was supposed to cool down. So there was, in theory, decidedly less of a chance of killing your CPU by having the heatsink meet it in an unfortunate angle, or something to that effect.

Unfortunately, the spacer that I had bought turned out to be just a wee little bit too thick, and, despite thermal paste (Arctic Silver!), the CPU did not in fact make contact with the heatsink (something shiny from Thermalright or Zalman, I think?) at all, which killed it instantly as soon as I powered up the rig for the first time. That's what it was like back in the days, when we got to school walking ten miles uphill (both ways) barefoot in deep snow.

I had to put in some overtime at the small PC shop I worked after school back then, to afford a measly Duron 800 as its replacement. And still they keep claiming that time heals all wounds... ;)

Injustice ;)

During pgConf.eu in 2016(-ish, could have been one or two years later; I don't remember too well), a representative of payment processor Adyen told the audience that they were, essentially, one big postgres cluster in their backend, too ("cluster" used as per the postgres-native meaning of the term, as in, an installation on a single host with a data directory containing any number of databases).

Ftr, I think you are being needlessly harsh. I enjoyed reading OP's story.

My personal favourite use of the colon command is what I've written about some years ago: https://johannes.truschnigg.info/writing/2021-12_colodebug/

I guess it is, but solar can only be part of the answer: You need a solid plan (and all the infrastructure that implementing this plan involves) for when the sun does not shine, because in the more northern parts of Europe especially, energy consumption is highest during seasons in which sunlight is (relatively) scarce.

Also, "the grid" cannot absorb any amount of solar energy - so if you choose to address (at least parts) of the above challenge with a photovoltaic build-out that results in massive excess capacity during summer, there needs to be a plan (and again, its implementation) to handle that.

Long-term, that's the smart and also necessary move. But it can't be done overnight, and the transition has its significant challenges. I hope they don't mess it up it and will address these problems rationally - but given how most EU leaders have acted over these past few years, I remain painfully unconvinced that they will.

Netgear GS308T, Netgear GS108T v3, and HPE JG925A.

With the 25.12 release, the luci app to use ASU for upgrades became installed by default in OpenWrt's "vanilla" images the project builds and provides for supported hardware and devices.

Previous OpenWrt releases at least as far back as 21.02 could be equipped with the same degree of ASU support by installing a single package (luci-app-attendedsysupgrade) and its dependencies.

Your OpenWrt ecosystem knowledge seems oudated; upgrades are a solved problem since the advent of "Attended Sysupgrade": https://openwrt.org/docs/guide-user/installation/attended.sy...

It's been included in all suitable default image configurations starting with OpenWrt release 25.12.

I do run OpenWrt on my x86-based router, on my AP, and even on my managed switches, and have no regrets.

Windows actually needs to be laid to rest forever. Win32 may live on as a legacy/stable API (via WINE) on superior free and open platforms.

Living in a city in Europe in a very decent apartment in a building that was erected in the 1880s (sic), this article made me chuckle - but also feel bad about how the throwaway society of the 21st century has extended even to things that are supposed to last.

We use this technique in our team to distribute passphrases for our secondary secret stores (that contain instructions on how to access our primary secret stores) in a "democratically secure and safe" manner.

https://packages.debian.org/trixie/ssss is a nice and rather straightforward implementation.

I recommend https://johannes.truschnigg.info/writing/2025-02-simple_effe... as an (imo) better approach than fail2ban parsing your logs to deal with the problem.

One of my most esteemed former co-workers used to say that whenever you succeed in making something idiot-proof, the universe will create a better idiot, undoing any progress you made.

Does Windows on ARM use VBS/Virtualization Based Security, and does ARM support nested virtualization to do so in a VM, too? Does it employ costly CPU vulnerability mitigation techniques that might hit two times in a VM (unless the Hypervisor is adequately set up, which I'd hope is the default for Hyper-V)? Those two things account for most of the common performance problems observed when putting modern Windows in a VM. I'd love to know more about it, but the article does not seem to mention either.

I'd say it's either because they're just having fun, or because they're dumb.

Thanks for this (and I actually learned about PS1's handy Unblock-File this very moment! :)), but I am aware of the "mark of the web"-stuff MSFT had introduced after realizing that an "attacker-controlled" filename extension alone is a poor safeguard against making a file executable ;)

For my specific problem/situation, the executable in question gets transferred to the target machine on a read-only UDF file system burnt onto a USB thumb drive. Other Golang executables from FOSS projects on the same filesystem execute just fine (I guess they have better "reputation", due to their hashes being registered with MSFT somewhere).

"works just fine on Windows as it always has" is just not true. These days, I cannot even run my own cross-compiled Go executables of a cross-platform tool that I am developing in private on Windows 10 or 11, because some blue popup from Windows Defender/"SmartScreen" prevents me from doing so, and tells me to contact the software publisher if I'd like to be able to do something about it. Outright disabling Defender/SmartScreen works around the problem (but the popup doesn't tell me that), and, presumably, signing these executables with a "trusted" developer certificate would make this outcome less probable - that is at least what people online have been telling me.

In my book (I started using computers during ther Windows 3.0 era), this clearly does not qualify as "working just fine on Windows as it always has", no matter how you spin it.

As a wireguard user myself (even on the lone Windows machine that I still begrundingly have), I am happy that this problem could have been resolved. I am just wondering - if there had not been this kind of public outcry and outrage that Mr. Donenfeld discounts in his announcement message, would the issue have been fixed by now?

What are individual developers of "lesser" (less important, less visible, less used) software with a Windows presence to do? Wait and pray for Goliath to make the first benevolent move, like all the folks who got locked out forever from their Google accounts on a whim? Ha!

The fact of the matter is, the code signing requirements on Windows are a serious threat to Free and Open Source Software on the platform. Code signing requirements are a threat to FOSS on all platforms that support this technique, and infinitely more so where it's effectively mandatory. I firmly believe that these days, THIS is the preferred angle/vector for Microsoft to kill the software variety their C-levels once publicly bad-mouthed as "cancer", and zx2c4 is one of the poor frogs being slowly boiled alive. Just not this time - yet.

I am already donating the rough equivalent of the cheapest Microsoft 365 subscription to The Document Foundation each year, and won't stop now just because they're increasing the visibility of their donation-based funding model. I hope they succeed, and many more people start contributing financially as a result.

Thanks, but no thanks. The only winning move, long-term, is to excise everything this wretched company makes from your life as vigorously as possible. It's been true 20 years ago, and it's even more true today.

None of the missing ones have proper, official, upstream LineageOS support. If you install LineageOS on these, you install somebody's own, personal fork of LineageOS. Which might be totally fine, of course. But because of the necessarily different signing keys alone, it's a (potentially) very different thing.