hearthstone-linux VS linux-hardened

Furthermore, because you didn't name Distrobox, is it fair to assume that you're not making use of it? Back when I started, I didn't know much about Nix. So my go-to (when a flatpak didn't exist) was to go directly for a distrobox with a custom home folder (at least I could get rid of everything contained within when I felt like it). And I'd argue it has been instrumental in easing the experience until I got more comfortable with how Silverblue is used. Heck, even now I've got a dedicated Arch-distrobox with Wine for the times Bottles fails me. I also just recently made another Arch-distrobox for a native install of HearthStone for some experimentation with getting the Deck Tracker to work in it while all being properly confined (still WIP). I can't remember the amount of times I tried some random stuff in a(n ephemeral) distrobox (like installing cmatrix for the heck of it), get some enjoyment/fulfillment out of it and just continue with my life afterwards. I feel like with Distrobox, you'd have a much easier time on Silverblue. At times you can afford to rethink/relearn your ways to do it more accordance to the 'Silverblue-way'; one-step-at-a-time. But sometimes you can't, or for some reason it just doesn't seem to work. For such cases, instead of reverting back to Workstation, you should instead use Distrobox to get the work done.

i followed this guide https://github.com/0xf4b1/hearthstone-linux, and it worked perfectly for some months, but now whenever i start hearthstone it wont let me log in and im met with this message:

You can easily install it using lutris or you can even install it without using wine/lutris https://github.com/0xf4b1/hearthstone-linux

The OSX version of HearthStone uses the Unity engine, using the Unity/OSX version it is possible to get Hearthstone running on Linux without wine or similar compatibility/virtualization layers.

You actually CAN use decktracker if you install it via lutris contrary to what some people say here. Google arena tracker, works good enough. But here is another issue, I don't know how for others, but for me game might suddenly just get stuck, and moreover you won't be able to get back instantly because battle.net takes so much to launch on lutris. It happens really rare. But when it happens on 10-2 arena run or when you are 2 stars from legend... You could also install it as native game which works absolutely flawlessly, https://github.com/0xf4b1/hearthstone-linux, but here you won't be able to use decktracker ( at least I don't know how, if you know how, I'll be happy know )

Glossing over their hardening guide, we notice that the kernel-hardened package is mentioned. This is a fork of what once was the kernel of GrapheneOS. While this hardened kernel can be used on a variety of distros, unfortunately this doesn't apply to Fedora Silverblue. Furthermore, I haven't seen any mention of the hardened kernel being used on openSUSE Tumbleweed. Therefore I see no reason to believe that this is possible on openSUSE Aeon either. Though, I'd love to be corrected on this!

Here's the GitHub page for the linux-hardened package in the official Arch repos. You will find that lots of changes come from GrapheneOS. "Forked from GrapheneOS" is in tiny, tiny text near the top-left of the web page underneath the project name.

Here is the source code for the hardened Linux kernel.

so that we can use it liberally in CLI) > **Additionally, here's a 'building from the source section** - https://github.com/firecracker-microvm/firecracker/blob/main/docs/getting-started.md#building-from-source ### Running Firecracker > "*In production, Firecracker is designed to be run securely, inside an execution jail, carefully set up by the jailer binary. This is how our integration test suite does it. However, if you just want to see Firecracker booting up a guest Linux machine, you can do that as well.*" 1. We need to first obtain an "uncompressed Linux kernel binary, and an ext4 file system image (to use as rootfs)" ; great, these are two things that we need to seek out before we move forward in our 'adventure' (*this really feels like a "quest" of some sort, like the ones that they forced you to play on Runescape back in the days*) **How to Decompress Linux Kernel** (explicit instructions to be honest here) - https://0xax.gitbooks.io/linux-insides/content/Booting/linux-bootstrap-5.html **Linux-Hardened Kernel** - https://github.com/anthraxx/linux-hardened (this is something that they're all still actively working on at this very point in time) They also say that we need an 'ext4 file system image' (where do we obtain this from?) - found it **Full Guide on How to Create an EXT4 filesystem image here** -https://fabianlee.org/2020/01/13/linux-mounting-a-loopback-ext4-xfs-filesystem-to-isolate-or-enforce-storage-limits/ Assuming that the above has been handled, the directions insist that we create two separate shell prompts, (one to run Firecracker, and another one to control it [by writing to the API socket]; both shells have to run "in the same directory where the firecracker binary was placed") ^^ What? - This is a pain in the ass because this is something that they should've mentioned earlier (obv. everyone is going to move a binary where the rest of their binaries go ; and you're not going to just load up some random project to be used in that manner) - Not even sure what the end goal of opening up an API socket here would really be But fuck it, let's just assume that we play ball and we adhere to all of these (additional) steps that we're being put through (just for the setup up this virtualization tool!). ### Following Through on the Next Steps 1. Ensuring that Firecracker can create its own API ``` bash rm -f /tmp/firecracker.socket

Officially supported kernels Community support on forum and bug reporting is available for officially supported kernels. Stable — Vanilla Linux kernel and modules, with a few patches applied. https://www.kernel.org/ || linux Hardened — A security-focused Linux kernel applying a set of hardening patches to mitigate kernel and userspace exploits. It also enables more upstream kernel hardening features than linux. https://github.com/anthraxx/linux-hardened || linux-hardened Longterm — Long-term support (LTS) Linux kernel and modules. https://www.kernel.org/ || linux-lts Zen Kernel — Result of a collaborative effort of kernel hackers to provide the best Linux kernel possible for everyday systems. Some more details can be found on https://liquorix.net (which provides kernel binaries based on Zen for Debian). https://github.com/zen-kernel/zen-kernel || linux-zen

Overall those patches do protect you in a lot of cases. Per default upstream features are chose to honor security first. Furthermore patches do frequently protect against upstream failures and vulnerabilities. One of the latest examples is CVE-2022-1729 https://seclists.org/oss-sec/2022/q2/122 a local privilege vulnerability that linux-hardened simply protects since before day 0: https://github.com/anthraxx/linux-hardened/commit/4dd6bdf3b079ef73e597661ee961d225bfccbe2a On top the approach in several places of fail-early instead of potentially continuing with known corruption or certain use-after-free regularly uncovers problems that get fixed upstream and where the vanilla kernels just keep on running, which include exploitable problems. One example of a faulty very recent commit that has been bisected and fixed because of linux-hardened: https://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git/commit/?h=for-next&id=acde4003efc16480375543638484d8f13f2e99a3

Those two don't protect the kernel itself from "misuse". To do that, there are ways like kernel hardening 3, using hardened kernel 4 5.