Vulkan 1.3 on the M1 in 1 month
- 0 Followers
- 0 Following
- 0 Posts
Release: Getting Started with Endless OS 6 — Available Now!
rpm-ostree currently does not support DKMS, and it’s unlikely that’ll be implemented anytime soon, if ever. It does support akmods, though, which is the preferred way to build Kernel modules on Fedora. You could ask if the packager can build that way to support the Fedora Atomic editions.
If you need these Kernel modules now, I think your only option would be to build manually from source, but that has the downside of requiring a manual step every time the Kernel is updated.
@[email protected] @[email protected]
A fix has already been published to Steam stable on Flathub. Workarounds can be removed now.
The last commit on that repository was 7 years ago, seems unmaintained. I wouldn’t recommend using this.
If someone decides to use it anyway, don’t use their udev rules. Just install steam-devices or game-devices-udev instead. If you don’t have those packages available in your distro, all rules can be found in the git repo https://codeberg.org/fabiscafe/game-devices-udev
You shouldn’t use
sudo to run powerprofilesctl
Will CIQ’s new support program alienate the community it built on an objection to subscriber-only services?
Will CIQ’s new support program alienate the community it built on an objection to subscriber-only services? - Lemmy.World
Gordon Messmer on fosstodon: [https://fosstodon.org/@gordonmessmer/111958736800454840] CIQ built a community on an objection to subscriber-only services, only to build a new subscriber-only service. Will their community accuse them of betraying Open Source? https://medium.com/@gordon.messmer/will-ciqs-new-support-program-alienate-the-community-it-built-on-an-objection-to-subscriber-only-fb58ea6a810e [https://medium.com/@gordon.messmer/will-ciqs-new-support-program-alienate-the-community-it-built-on-an-objection-to-subscriber-only-fb58ea6a810e]
you are vulnerable during pairing which is for like a minute.
I said this twice on the PSA: it’s hard to tell if your device is in discoverable mode, and it’s easy to forget it in that state, or start it accidentally. I’ve caught my devices accidentally in discoverable mode many times. You could have your PC a whole week in discoverable mode and never notice it, just by having a settings window left open.
It’s more risk than most people should take, hence the warning.
Still, if you’re comfortable with the risk, you’re free to change the config and allow insecure devices.
The controller itself is insecure, it doesn’t exactly conform to Bluetooth standard. There’s no indication Sony ever planned cross-compatibility, the DualShock 3 was made to be used only on the PS3 console, where the lack of authorization supposedly wouldn’t be a problem.
Of course, you can still use it on a system where you can accept the risk, as well as on the PS3, or wired. The controllers are not e-waste yet.
PSA: Bluetooth vulnerability and PS3 Controllers on Linux in 2024
PSA: Bluetooth vulnerability and PS3 Controllers on Linux in 2024 - Lemmy.World
cross-posted from: https://lemmy.world/post/11498269 [https://lemmy.world/post/11498269] ># PSA: Bluetooth vulnerability and PS3 Controllers on Linux in 2024 > > In late 2023 a Bluetooth vulnerability CVE-2023-45866 [https://access.redhat.com/security/cve/cve-2023-45866] was discovered and patched [https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=25a471a83e02e1effb15d5a488b3f0085eaeb675] in Bluez. By now, this vulnerability should be fixed on all Linux distributions. The fix has one compatibility implication: support for insecure legacy devices is now disabled by default. The Sony PlayStation 3 Controller (AKA DualShock 3 or DS3) is probably the most notable device affected by this change. > > ## What to do if you have a PS3 Controller > > The PS3 Controller should still be plug-and-play on Linux when used wired, this change only affects wireless use. > > Wireless use is now disabled by default. It should still be possible to use the controller wirelessly with a configuration change, but that will make your PC vulnerable when Bluetooth is in discoverable mode — that’s when you’re pairing a device; in GNOME that’s when you just have the Bluetooth settings open; easy to have on by accident. > > It’s painful for me to say this (I own several PS3 Controllers), but the DS3 is reaching its end-of-life, and we should start to consider moving on from it as a gamepad for PC. > > ## How to re-enable Bluetooth support for the PS3 Controller > > This is insecure: It will make your PC an easy target for remote code execution attacks from anyone in close proximity whenever your Bluetooth is in pairing/discoverable mode. It’s usually hard to notice when Bluetooth is in discoverable mode, and it’s very easy to accidentally leave it on. You have been warned. > > TL;DR: The following command should do it, tested on Fedora 39: > > shell > sudo sed -iE -e 's/^#ClassicBondedOnly=.*/ClassicBondedOnly=false/' /etc/bluetooth/input.conf && sudo systemctl restart bluetooth > > > Long version: Use the configuration file at /etc/bluetooth/input.conf, under the [General] section, add the option ClassicBondedOnly=false, then restart the bluetooth service or reboot the computer. Your config file should look like the following: > > toml > # Configuration file for the input service > > # This section contains options which are not specific to any > # particular interface > [General] > > # Set idle timeout (in minutes) before the connection will > # be disconnect (defaults to 0 for no timeout) > #IdleTimeout=30 > > # Enable HID protocol handling in userspace input profile > # Defaults to false (HIDP handled in HIDP kernel module) > #UserspaceHID=true > > # Limit HID connections to bonded devices > # The HID Profile does not specify that devices must be bonded, however some > # platforms may want to make sure that input connections only come from bonded > # device connections. Several older mice have been known for not supporting > # pairing/encryption. > # Defaults to true for security. > ClassicBondedOnly=false > > # LE upgrade security > # Enables upgrades of security automatically if required. > # Defaults to true to maximize device compatibility. > #LEAutoSecurity=true > > > I’m posting this PSA on [email protected] [/c/[email protected]] and [email protected] [/c/[email protected]]. Please forward this message to other interested Linux communities. >