this post was submitted on 06 Aug 2024
33 points (100.0% liked)

Linux Gaming

15902 readers
5 users here now

Gaming on the GNU/Linux operating system.

Recommended news sources:

Related chat:

Related Communities:

Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.

founded 4 years ago
MODERATORS
 

Hey all. I'm heading to Quakecon 2024 tomorrow and will be repping the penguin. I've got all my games set up and ready, but was now wondering, are there any extra steps I should take as far as network security goes?

I'm sure I'm not as vulnerable to random badness as the flock of Windows machines that will be on the network, but you never know. The only thing on my list so far is to disable sshd. I thought about installing Portmaster but it has always messed up my DNS in the past...

I'll probably run Wireshark just to see if I can capture anything interesting there. Do you all have any other suggestions for prepping my PC?

top 19 comments
sorted by: hot top controversial new old
[–] ryannathans@aussie.zone 17 points 3 months ago* (last edited 3 months ago) (1 children)

Checking the basics.. You got a firewall right? It's on? Ports closed?

Are you going to leave your pc unattended? At all?

[–] pelotron@midwest.social 6 points 3 months ago (4 children)

Negative - that's why I was thinking of giving Portmaster another go but am open to any solution like that.

Yes the PC will be unattended for many hours at a time.

[–] gaylord_fartmaster@lemmy.world 19 points 3 months ago (1 children)

I'd just install UFW and either set the default for incoming and outgoing to deny and unblock the game ports manually, or just set incoming to deny and outgoing to allow.

You could pair that with OpenSnitch to see all attempted incoming and outgoing connections and block them by default, and then just allow the ones you want as they happen.

[–] pelotron@midwest.social 5 points 3 months ago

Thank you for these suggestions! I've been looking for something like Opensnitch for a long time.

[–] ryannathans@aussie.zone 6 points 3 months ago

Unattended? I'd use a bios password and disk encryption

[–] ReversalHatchery@beehaw.org 2 points 3 months ago (1 children)

Yes the PC will be unattended for many hours at a time.

Check out usbguard, whitelist your own devices, preferably no USB drives.
The ArchWiki has a good article on it. I don't use arch, btw.
Other than that, maybe check every time you get back to the machine that your keyboard still directly connects to the machine, without an intermediate device (yes, even with usbguard), but at that point maybe just always keep your keyboard with yourself because a really motivated attacker could just place some kind of keylogger inside of it.

Maybe also look into hardening your lock screen, or finding a simpler one that's perhaps more security oriented.
Maybe it's not the case anymore, but once it was possible to unlock a locked account by crashing the screen locker. Possibly that's not the case anymore, because I remember having to type loginctl something in a new virtual terminal when my lock screen crashed after an update gone bad, but i wanted to make you aware so you can check if you are affected.

[–] pelotron@midwest.social 1 points 3 months ago

Ooh, usbguard sounds cool.

[–] pcr@scribe.disroot.org 1 points 3 months ago

You might find it helpful to look up "Evil Maid Attack" as you will be susceptible to that.

[–] tetris11@lemmy.ml 9 points 3 months ago (2 children)

I recommend gumming up the USB ports with chewing gum, and then wrapping the whole under case in a condom with airholes. Finally, lather any exposed peripherals with butter and marmalade, and walk by occasionally to just make intense eye contact and fart.

If that doesn't work, I don't know what will.

[–] Akasazh@feddit.nl 3 points 3 months ago

This guy lans

[–] Nemoder@lemmy.ml 9 points 3 months ago

I guess if you want to be paranoid you could get a new hard drive and install just what you want for the LAN and keep personal info off it. Then just swap back when you get home.

[–] ReversalHatchery@beehaw.org 9 points 3 months ago* (last edited 3 months ago) (1 children)

Not network related, but don't keep very personal info on it while you're there. Log out of mostly all sites, or just clear the cookies (all of them), and only keep passwords accessible through it that you might need there. Log out of your primary password manager, or if it's offline, move your primary password db to a different machine for the time you're there

[–] pelotron@midwest.social 2 points 3 months ago
[–] OsaErisXero@kbin.run 8 points 3 months ago

Update your bios, grab a clean disk image before you go, nuke it from orbit when you get back and restore from backup.

[–] thomcat@midwest.social 5 points 3 months ago

Make sure your BIOS is up to date

[–] perishthethought@lemm.ee 4 points 3 months ago

Install Fail2Ban, maybe?

[–] Giloron@programming.dev 1 points 3 months ago

Don't know anything recent, but years ago they began blocking network traffic between rows. That killed what little self hosted LAN play was still happening but kept stuff from spreading across the whole BYOC.

[–] boatsnhos615@lemmings.world 0 points 3 months ago

Don't go, it's a trap