That is a setup guide for hardware key and passkey auth. It is not a hardening guide, and does nothing to mitigate these LPE vulns.

Just to throw out an easy option: if the music is well-labeled on Youtube, you can get pretty close to that full suite with just yt-dlp by using --embed-thumbnail as a stand-in for album art, dumping your files with an “Artist - track - album” naming structure using the --output-template flag — then using an awk or python script as a second pass to add the artist/track/album names to each file as tags.

E: and in case it isn’t self-evident, you don’t have to give yt-dlp a URL for each track; it’ll work fine with a playlist URL.

Yt-dlp is the gold standard for that.

https://github.com/yt-dlp/yt-dlp

Tag cleanup and album art are their own beast that you’ll wanna tackle post-download, but beets is another gold standard tool that can help with that layer.

https://beets.io/

No need to cargo-cult security practices here, chief. You’re not gonna get pwned by publishing your hardware specs. If you’re planning to build some kinda webapp for yourself, that’s a different story - but you have to fuck up hard to get hacked while hosting raw HTML.

Use an SSH key, disable password auth, make sure you’re firewalled (i.e. test with nmap), and call it a day.

Is there a buried lede here? What’s noteworthy about an RC of a minor version release?

This isn’t storing the game in RAM; it’s caching it — which isn’t an effective strategy if you actually want fast load times and do any sort of substantial disk IO between system boot and game launch.

Not tryna get too analytical on a meme post, but tmpfs is the correct way to do this for anyone wanting to pull this sorta thing off seriously.

While I’m sure there’s a pre-canned tool out there for you, if you have basic software experience (which you seem to), this is one of those times where it’s usually most efficient to hack together a dumb CGI script and call it a day.

This prompt should get you most of the way there, using your llm of choice:

Write a minimalist cgi script to help upload files to a server. Upon a GET request, serve a light page with a centered form that takes in a file and a submission code. Submission codes will be stored on individual lines of a plaintext file. Adding new codes to this file is out of scope - but the codes will be 8-char hex strings (do validate that submission strings are not empty!). The script should accept the submission as a POST, and save the file to an upload dir if the submission code is valid.

Vet the output, harden as needed, setup a systemd service to serve with busybox httpd, and optionally reverse-proxy. If you’ve done this sorta thing before, you can probably knock it out in a half hour.

I’m talking about the executable binary flatpak, which is the interface used to execute and manage applications distributed in the Flatpak bundle format.

https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak

Flatpak: a system for building, distributing, and running sandboxed desktop applications on Linux.

Flatpak application: an application installed via the flatpak command or through a graphical interface, such as GNOME Software or KDE Discover.

Runtime: also called platform, an integrated environment providing basic utilities needed for a Flatpak application to work.

Flatpak bundle: a single-file export format containing a Flatpak application or runtime.

From https://docs.flatpak.org/en/latest/introduction.html#terminology

You might be thinking of AppImages, which are more of a pure file format.

Ah - I totally missed the Nvidia-related bit! Thanks for flagging that.

That being said, based on the maintainers’ past stances, I’m pretty pessimistic on them actually implementing a fix like that. They’re very much against the general practice of poking holes in their sandbox security perimeter.

Flatpak is quite fucking far from perfect, and will always remain so due to its flawed design and UX approach.

Pretty sure the culprit here is Fedora’s packaging which adds an opaque systemd timer to run auto-updates, but the thread immediately next to this one on my homepage just happened to be a nice case-study in Flatpak fuckery: https://lemmy.world/post/30654407

Of course, the proposed changes in the article do nothing to fix this sorta problem, which happens to be the variety that end users actually care about. Flatpak is an epic noob trap since it pretends to be a plug-n-play beginner friendly tool, but causes all sorts of subtle headaches that newcomers inevitably don’t have diagnostic experience to address.

Object storage is indeed a specialized filesystem in a trenchcoat.

Object storage is typically (but not always) associated with non-hierarchical key-value lookups, as opposed to the directory tree pattern most file systems use. Object storage systems are also typically (but not always) designed with sharding and distribution in mind.

I was hoping to play around with the dataset over the weekend to toy with some text-embedding techniques, but they’ve pulled the cord on the download links.

Anyone have a copy of the full archive they’re willing to share, or a magnet link?

Synology runs a proprietary OS OOTB that’s had multiple sloppy vulns exposing full remote access to users’ files. Putting your data in the hands of fuckups who have and will continue to leak it is the opposite of total control.

It’s completely trivial to store any data you want to in a cloud provider 100% securely just by piping it through openssl before uploading.