>"They aren't printing every single part of the gun, but yeah, they are printing guns."

Well, no. They are printing parts of guns, not a whole gun. The barrel is certainly not printed. Nor are springs, fasteners, striker, etc.

>"You can make your own rifled barrels with EDM"

At least for now, [essentially] nobody has an EDM machine at home. And this is no different from just making parts with metal machining tools. Are we going to ban/restrict metal lathes and such? Or force computers on them so they can somehow detect you are manually making a barrel, trigger, firing pin, charger, springs, etc?

>"so you actually can manufacture every part of the firearm yourself."

Right. You could always do that. This new stuff doesn't really change that much. And it doesn't replace needing metal work. It might make some things easier, but still requires a lot of work/time and some expertise.

>"This is another instance of gun nuts ruining things for the rest of us."

Please define "gun nuts" because exercising your constitutional and lawful rights to be able to defend yourself and others is not nutty. And printing accessory parts isn't really all that nutty, either. People aren't "printing guns", at least not with plastic printers.

Your ire should be pointed squarely at the people at fault for making this mess- legislators who are apparently completely clueless about both firearms and technology.

>"The new Harleys have a feature that randomly dumps oil on the ground to mimic the classic HD experience."

You forgot the horrible out-of-balance vibrations, strange noise, and mediocre performance. Then you would get closer.

There is a reason I ride a 16 valve inline 4 with variable valve timing (and stock muffler).

>"Frankly I'm thinking... whatever it takes to sell bikers on replacing their painfully noisy kill-me machines with silent kill-me machines is worth it."

They are only loud if illegally modified. Mine is no louder than most cars.

The problem with electric motorcycles is that there is not enough room for batteries. Until you can produce something with 160+hp per 600lbs *AND* 250 mile range, not interested.

>"Gotta have that phone in case there's a school shooting."

Um yeah, sure. But that doesn't require unrestricted internet/app access.

>"following pressure from parents who claim too much in-school screen time has zapped children's attention spans and left them worse off academically."

And how many of these parents gave their children phones/tablets/computers with full internet/app access?

>"seriously? of course firefox users fucking complained. That's why the mozilla had to add their AI kill-switch after they got caught auto-adding AI."

No. Mozilla never "added AI". They added the ability to optionally hook Firefox into third-party AI systems (with the default on). And there was ALWAYS AN OFF SWITCH. It just wasn't in the main settings, it was under about:config. Then they later added in the main settings as well.

It never downloaded or installed any AI system. Very different.

>"I've gone and deleted chrome. I'm using Brave, but its crypto-bros in charge of that so I dont exactly trust them either. They just have a really effective adblocker that doesnt seem to trigger youtube into issueing shrill threats about breaking TOSs with adblockers"

I would suggest Firefox + UBO. I have no problems on YouTube or other sites with them (at least that is my experience on my machines which all run Linux). And as a huge bonus, you get to NOT support Google's efforts to control the web (Brave is still based on Google Chromium). Plus you also signal to sites that you want to support actual browser diversity, not mostly just a different UI on yet another Google-controlled engine.

>"Quick - copy and paste all your comments from the "Copy Fail" discussion over here!"

Pretty much :) It is essentially the same issue, found in three other kernel modules. Alma Linux and others already have pages up about it. These are serious issues for multiuser/multitenant servers needing to mitigate immediately. Not so much for single-user or home systems.

Copy Fail used the algif_aead module and for enterprise Linuxes, that is built-into the kernel. So either update the kernel, or mitigate with:

# grubby --update-kernel=ALL --args="initcall_blacklist=algif_aead_init"

and reboot. Dirty Frag uses three additional modules: esp4, esp6, and rxrpc. Enterprise Linuxes don't build those in, so all distros should be able to use something like:

# rmmod esp4 esp6 rxrpc
# sh -c "printf 'install esp4 /bin/false\ninstall esp6 /bin/false\ninstall rxrpc /bin/false\n' > /etc/modprobe.d/dirtyfrag.conf"

for immediate mitigation, without rebooting. Of course, disabling those modules has a price, it will disable IPsec ESP, IPsec VPNs (like Swan), and AFS clients. So if you use/need those, you can't mitigate without losing that functionality.

Thanks! That was very informative (and not something I could easily find).

I remember playing Rogue way back in the 80's on ASCII terminals :) Many hours. I think I moved on from that fad before NetHack appeared. It is cool that there is an X11 version for Athena and QT, too.

Now I am getting nostalgic.... I remember when we were on X Terminals, Xblast TNT came out. Great times blasting other players on the network. Wow- it is still in the Mint repos, and as a native package! https://community.linuxmint.co...

I know version numbers are often arbitrary, but why did it jump from 3.6.7 to 5.0? Do they not like the number 4?

The manufacturers aren't the problem. They aren't the ones who make the rules about how their product is used on public thoroughfares.

The context of that phrase is almost always used for people who invite regulation with their own foolish/dangerous behavior.

>"I am not sure if there are any negative ramifications of having algif_aead disabled, though. Does anyone know?"

According to my research, it isn't used on most systems.

"Disabling algif_aead typically does not break anything, as most programs use userspace libraries instead of relying on this kernel module. It is noted that only a few specific applications, like iwd and cryptsetup with certain non-default algorithms, may be affected."

For older enterprise distros, this mitigation method:

# echo "install algif_aead /bin/false" > /etc/modprobe.d/disable-algif.conf
# rmmod algif_aead

Does not work because algif_aead is built into the kernels.

However, this does work:
# grubby --update-kernel=ALL --args="initcall_blacklist=algif_aead_init"

Then reboot. It will disable the vulnerable module that is built-in. I am not sure if there are any negative ramifications of having algif_aead disabled, though. Does anyone know?

Updating to a patched kernel is, of course, the better course.

See https://seclists.org/oss-sec/2...