Steam system requirements say RX5700 minimum. Recommended is RX6800XT, which was ludicrously expensive last I checked. Also I need a much newer CPU.
In this economy, that’s gonna be a no from me.
Steam system requirements say RX5700 minimum. Recommended is RX6800XT, which was ludicrously expensive last I checked. Also I need a much newer CPU.
In this economy, that’s gonna be a no from me.
Who the hell are they expecting is going to play this game? Only trust fund kids?
[meme where the hero pulls the mask off the tied-up Firefox’s head, revealing Safari]
“Pirates? I’m sorry, I can’t hear you over the gazillion sales we’re about to make.” —Bethesda, probably
Why would you want to play a Bethesda game 5 days early? The best time is several months after release, when the community has had time to fix the bugs.
As is Bethesda tradition.
Note that for vector graphics editing, Inkscape is really good. That doesn’t help you if you need to edit photos, though.
KDE has neat stuff, but Compiz was the king of bling.
Linux. I signed up with my first proper ISP as a kid in the '90s. The service included a shell account on their Linux server accessible by telnet. I thought it was really cool and decided to see if I could run it on my own computer, and to my delight, I could.
Are you going to elaborate, or…?
Here’s my advice:
Disable password authentication and allow only key/certificate/token/etc wherever feasible. Don’t even ask for a password if some other authentication mechanism can be used instead. Human-memorized passwords are weak and generated passwords are a poor substitute for proper cryptographic key exchange.
su
, sudo
, and Polkit are privilege escalations waiting to happen. Remove them if possible; deprivilege them (remove the setuid bit) if not. Do not allow any means for an unprivileged user to get a root shell, regardless of authentication, because unprivileged accounts may be backdoored and letting them elevate will grant root privileges to the attacker as well.
On your local machine, always log in as root on a separate virtual console using a separate password. On remote machines, always log in as root using an ssh key only accessible to the root account on your local machine.
I’m iffy about hiding SSH behind a VPN. Doing this creates a serious risk of being locked out of your own server, and if your SSH server is configured correctly (as described above), then the security benefits aren’t that big. If you do find the risks acceptable, feel free to do this, but you shouldn’t feel obligated.
Docker is unnecessary complexity and overhead. Use systemd to isolate things; it can do things like filtering system calls and hiding portions of the file system. SELinux might be good too, if you can figure out how to use it (I never could).
Fail2ban is unnecessary if nothing accepts passwords for authentication. There are no fails to ban.
I’m an adult with a job, and I don’t have a snowball’s chance in hell of affording the recommended system requirements for this game any time soon. RX6800XTs do not grow on trees.