You're viewing a single thread.
You're in good company. Steam even managed to do it for a whole bunch of people:
https://github.com/ValveSoftware/steam-for-linux/issues/3671
I remember this lol, to be fair no one knew how the guy managed todo it, because steam(the launcher) has checks for that, they assume the guy tried to run the steam command instead of clicking the launcher(don't do that)
Holy... Fuck... That is scary AF!
and THAT, children, is why I run steam in a jail. Fuck the idea of giving access to my home folder or anything else under my user...
Firejail?
yes, and I know it's less than perfect, but it's better than nothing :)
Makes sense.. I was curious what your solution was.. Sounds like I should invest some time into that .. Thanks.
On debian testing (trixie):
$ cat bin/steam-jailed.sh
#!/bin/sh firejail --private=/home/user/steamjail --profile=/etc/firejail/steam.profile ~/steam $1Sometimes an update breaks something, and I have to experiment with the profile settings, for which it helps to launch a bash with the same jail and start steam on the command line inside the jail to see output messages.
#!/bin/sh firejail --private=/home/user/steamjail --blacklist=${HOME}/.inputrc --profile=/etc/firejail/steam.profile bashWhat happens most of the time is that a steam update depends on a newer system library that I didn't yet install and I then have to do a system update - steam is shit at managing OS dependencies (i.e.: it doesn't)
Dude!! The is awesome! Thank you so much!