GrapheneOS supports this type of security checking outside of Google’s Play Integrity API but app devs have to enable it. The Graphene devs encourage leaving one star reviews, emailing support, and linking this page: https://grapheneos.org/articles/attestation-compatibility-guide
Agreed… depending on Google to implement or fix very specific features is just shouting into the void. Use a trusted 3rd party app like Bitwarden, as you mentioned
Seems like it needs a good old fashioned review bombing… https://www.amazon.com/Unhumans-Secret-History-Communist-Revolutions/dp/1648210856
Or during, and with open source it could have been possible for independent fixes to have been created as people figured out through trial and error. Additionally, something like this would have cost Crowdstrike a ton of trust, and we would see forks of their code to prevent this from happening again, and now have multiple options. As it stands, we have nothing but promises that something like this won’t happen again, and no control over it without abandoning the entire product.
Archive.org is essential. I donate regularly, they are a key part of the infrastructure of the internet now…
I use openSUSE Tumbleweed and it has BTRFS and snapper (snapshot manager) set up by default, with all necessary system subvolumes already created. It’s been a great experience for gaming so far, and actually the best experience with NVIDIA drivers I’ve had! All you would need to do is create a separate BTRFS subvolume and snapper config for your games folder and you’d be good to go, without worrying about any other setup! No need to use EXT4 at all. Additionally, there is very detailed snapper documentation on the openSUSE website.
Additionally, you can get support from the community in the openSUSE Matrix Space: https://matrix.to/#/%23space:opensuse.org
Use the support channel (#support:opensuse.org) or the gaming channel (#gaming:opensuse.org)
Yeah I believe asdf is a kind of package/version manager, so probably similar. And yes when you install you will see the Proton-GE version as an additional Proton version you can apply in the game options, but it does not overwrite the already installed proton versions
https://github.com/GloriousEggroll/proton-ge-custom
I recommend installing it via asdf, which is described in the installation section of the github readme
Just to be sure, you should check whether SSHD is enabled: sudo systemctl status sshd.service If you never enabled it and it’s disabled+inactive, then no need to reinstall Tumbleweed per the current guidance. Also you can double check your version of xz to make sure it’s downgraded, the downgraded version for Tumbleweed should look like this:
sudo zypper search -vi xz
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+------+---------+-----------------------+--------+------------------
i+ | xz | package | 5.6.1.revertto5.4-3.2 | x86_64 | update-tumbleweed
name: xz
Fairly simple explanation by arstechnica: “The malicious versions [of xz], researchers said, intentionally interfere with authentication performed by SSH, a commonly used protocol for connecting remotely to systems. SSH provides robust encryption to ensure that only authorized parties connect to a remote system. The backdoor is designed to allow a malicious actor to break the authentication and, from there, gain unauthorized access to the entire system. The backdoor works by injecting code during a key phase of the login process.”
Also from the article, you should check if your distro is offering a downgrade from the affected 5.6.x packages. Right now the exploit is not fully understood. For example, openSUSE recommends a full reinstall of Tumbleweed if an SSH server was enabled, just to mitigate risk.
Maybe because… automatically recording calls is literally illegal in some places around the world? It should probably be user choice to opt in to that so it wouldn’t be on by default. And then, if you have it on while travelling, you could forget and break the law when going through a jurisdiction that does not allow it. Better to explicitly allow for each call, like it does currently.
https://en.wikipedia.org/wiki/Telephone_call_recording_laws