My home servers have generally a lot smaller attack surface, as only a few ports are actually routed to them, so in theoey I could get away with a more relaxed approach. But I’m also a big believer in defense-in-depth, so I follow the same rules of thumb:

• iptables (or equivalent) that drops anything incoming that isn’t wanted. It also rejects anything going out that isn’t planned for.
• any public facing service (except ssh) gets its own user
• disable root login via ssh
• ssh login with key only on any user in sudoers

If I was on my laptop and not my phone I would post a screenshot with a P just for you

Well, there’s a footnote on my end: Me taking the drives home is a bit of a grey area, as the procedures say that the drives are to be mechanically destroyed when no longer needed. It doesn’t specify needed by whom. And I do attack them with my angle grinder, so it’s in accordance with company policy.

And yes, my employer knows and is OK with it. We go through a ridiculous amount of drives due to large storage needs, so pragmatism tends to trump bureaucracy.

I usually scavenge old drives from work. On one hand they’re a bit smaller than I’d like them to be, but on the other hand they’re free except from the minor work and documentation involved in ensuring that no company related data remain.

Yup, there’s no kinkshaming here

Well, he seems to be channeling some real Field Marshal Haig energy when it comes to losing soldiers

Same. My apathy of football is suddenly a virtue.

A few days ago I aked a dev at our subcontractor if this proprietary software would in theory run on windows. Not only “yes”, but me running mint on my worklaptop was perfect, because his dev and test environment was debian, so even though the software was built to run on windows, he could easily build a version specifically for me.

⚽️🧑‍🚀🔫🧑‍🚀

As some other megalomaniac learned in Iran recently: It takes two to TACO

deleted by creator

Resolution 1x1 with 1bit color depth. Nice.

I think the main problem here is that the source cited is openai themselves

Depends if you’re hosting something public, or something private.

For public, a webserver is a simple start. Can be anything you want it to be, but as complexity increases, so does the amount of potential attack vectors, so keep that in mind of you’re considering adding things like WordPress and the like.

For private, a NAS and/or a simple game server is a simple and useful start.

As for how, there’s a million ways to do it, and I’m an old stubborn BOFH that still cling to the old ways of doing it (as in, no VMs, no containers), so I’ll defer to others for that.

While purpose built server hardware is always nice since it comes with some useful additions, the truth is that “any” machine will do. Old discarded PC will do just fine.

They’re gathering intel in preparation for airdropping in Marco Rubio so he can go Just Cause on the island.

Fuck u/spez

4070 and mint on my laptop. No issues here.

deleted by creator

It was reasonably common in the floppy disk era. Some games allowed you to play for a set amount of time, after which it asked you for something external to the game itself. Some examples I remember:

• Dune 2 asked for some units stats that could be found in the games manual
• Day of the Tentacle needed you to complete a battery blueprint sketch in game. The missing info could be found in the manual
• Monkey Island 2 asked for a voodoo recipe. To find the correct measurements, you had to spin two overlaid sheets to align something, which revealed a value.

All of the above could of course be copied and/or guessed, but it did at least introduce some bar of entry.

This mostly comes down to your preferences, but my rule of thumb is that everything should be on mgmt vlan for mgmt, and then you choose which of those to expose to other VLANs via secondary interfaces. This has the benefit of allowing configuration when you’re on the management vlan only, and limiting access to the service itself.