this post was submitted on 24 Sep 2023
0 points (50.0% liked)

SteamDeckPirates

1697 readers
1 users here now

Discuss piracy on Valve's portable handheld - the Steam Deck.

founded 1 year ago
MODERATORS
[email protected]
0
Block Network Access for Game? (lemmy.ml)
submitted 1 year ago by [email protected] to c/[email protected]
8 comments fedilink hide all child comments
 

I know there are some tools including firejail and bindtointerface on standard Linux Distros, but they don't run in userland, so whenever the deck updates they will be overwritten.

Anyone have any ideas how to block access on a Steam Deck?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (1 children)

Have you tried OpenSnitch

[–] [email protected] 1 points 1 year ago (1 children)

Thanks for the suggestion, I think the main issue is doing it on the Steam Deck. On a native Linux machine it's easier. I don't see a way to install OpenSnitch on the Steam Deck with the read-only file system and whatnot. I think a pi-hole and block DNS might be easier than trying to mess with SteamOS.

[–] [email protected] 0 points 1 year ago* (last edited 1 year ago) (1 children)

You can't install applications on steam deck and there is a read only file system???? Whaaaatttt???????

Edit: I asked a friend that has a steam deck, he explained you can easily disable the read-only system, do whatever you want on a Linux system and reenable it afterwards.

[–] [email protected] 0 points 1 year ago (1 children)

From what i understand any changes to the system outside of the userland will be overwritten after a SteamOS update.

[–] [email protected] 1 points 1 year ago

That is correct. The best case is to write a script to make your desired changes, and then run it after each system update.
My own use-case is that I have a NFS mount-point for my Steam Deck to use extra storage on my NAS. After the first time I figured out how to get it mounted, I made a script to disable read-only filesystem, make all the changes to the system, and then re-enable read-only filesystem. After every system update, I just run that script once.