No touch screens, no telemetry, no cellular modems, no wifi, no apps, no subscriptions, no infotainment.

Knock knock.

Who's there?

I eat mop.

I eat mop who?

Eww, that's gross.

Github: https://github.com/oozebot/preFlight

Interested in taking some wild new 3D printing features for a test drive? preFlight is free and open source slicer that brings a host of processing improvements as well as fascinating new features and interesting twists on old ones. There are almost too many to list, so here are a few that caught our eye. Cross-sectional view of Interlocking Perimeters, which increases Z-strength. Unlike brick layers, layer height stays constant.

Want to mix and match different support types on the same object? No problem. How about use Nip & Tuck seams to better hide where layers start and stop? You can emboss images directly onto print surfaces with a real-time preview and use smart bridging for counter-bored holes. We particularly like the ability to preview a sliced object from the side instead of just by layer. That’s not all, either.

Those features alone are pretty intriguing, but there’s one in particular that is particularly relevant to creating stronger parts. Interlocking Perimeters increases layer bonding to increase object strength. Unlike brick layers, which staggers layers vertically, interlocking perimeters plays with spacing and compression to increase bonding in the Z axis while keeping layer heights constant. This is possible thanks in part to the greater control offered by Athena, the new perimeter generator.

There are plenty more features — like a full Python runtime embedded directly into the slicing pipeline, and a host of export pathways — so check out the GitHub repository for added detail and let us know in the comments if you give it a try.

Laugh track if you're unfamiliar with the term.

A new Linux zero-day exploit, named Dirty Frag, allows local attackers to gain root privileges on most major Linux distributions with a single command.

Security researcher Hyunwoo Kim, who disclosed it earlier today and published a proof-of-concept (PoC) exploit, says this local privilege escalation was introduced roughly nine years ago in the Linux kernel's algif_aead cryptographic algorithm interface.

Dirty Frag works by chaining two separate kernel flaws, the xfrm-ESP Page-Cache Write vulnerability and the RxRPC Page-Cache Write vulnerability, to modify protected system files in memory without authorization and achieve privilege escalation.

Also, while Dirty Frag belongs to the same class as the Dirty Pipe and Copy Fail Linux vulnerabilities, it exploits the fragment field of a different kernel data structure.

"As with the previous Copy Fail vulnerability, Dirty Frag likewise allows immediate root privilege escalation on all major distributions, and it chains two separate vulnerabilities," Kim said.

"Dirty Frag is a case that extends the bug class to which Dirty Pipe and Copy Fail belong. Because it is a deterministic logic bug that does not depend on a timing window, no race condition is required, the kernel does not panic when the exploit fails, and the success rate is very high."

This kernel privilege escalation affects a wide range of Linux distros, including Ubuntu, Red Hat Enterprise Linux, CentOS Stream, AlmaLinux, openSUSE Tumbleweed, and Fedora, which have not yet received patches.

​Kim released complete Dirty Frag documentation and a PoC exploit with distribution maintainers' agreement after an embargo on full public disclosure was broken on May 7, 2026, when an unrelated third party independently published the exploit.

"Because the embargo has currently been broken, no patch or CVE exists. After consultation with the maintainers on linux-distros@vs.openwall.org and at their request, this Dirty Frag document is being published," Kim said.

To secure systems against attacks, Linux users can use the following command to remove the vulnerable esp4, esp6, and rxrpc kernel modules (however, it's important to note that this will break IPsec VPNs and AFS distributed network file systems):

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

I was searching by "Most comments" and came across this 3 year old post in c/AskLemmy. It's been 3 years since that post, so I thought a follow-up would be interesting.

Original "Ask" Post: https://lemmy.world/post/1044707

Lemmyverse/Instance-Agnostic Post link: https://lemmyverse.link/lemmy.world/post/1044707

Courtesy of Rose and The Golden Girls.

I prefer D8 these days because I'm a lightweight and generally prefer the less intense buzz. I live in a state that's not recreational-friendly and don't qualify for medical (though I would in almost any other state, ugh), so I've been stocking up on D8 carts, gummies, and D8-infused hemp flower before the federal ban happens. Even if states can opt out as I've read might be an option, my state definitely will not.

What's the best way to store those long-term?

I've found freezing the gummies works wonders. A couple of years ago when state legislature banned D8, I had stocked up on gummies and put them in the freezer. I've still got plenty, and they're just as good as they were new even after close to 2 years in the freezer. So, I'm confident that works.

I also stocked up on carts back then, and I've had mixed results after a couple years. Some of them now taste absolutely terrible and others just clog up immediately. They were kept in a dark location but at room temperature. They're still mostly potent enough to get the job done, but not ideal due to the kinda gross taste and frequent clogs.

I just bought a new batch of carts and some pre-rolls, so what is the best way to deal with them?

What I've read are light and oxygen are the main things that cause it to break down. I've currently got the carts in ziploc bags with the air sucked out and am storing them in the fridge. I don't have a vacuum sealer, but I am looking to get one for the kitchen eventually and will probably upgrade the ziploc bags to proper vacuum sealed bags.

Is that sufficient, and any other tips to make these last?