zib

In my case, I use a PCI card with an m.2 slot for my OS drive. I lose a PCI slot, but I already had a few to spare.

I use a 1tb ssd for the os/apps with my raid5 strictly for storage. Kinda nice if the os needs to be reinstalled or I want to migrate the raid cluster.

Wait, are you telling me that business ethics are actually a real thing? I thought somebody made that up as a meme. Every corporate executive I’ve ever worked for has been a borderline, if not full blown, sociopath obsessed with nothing more than getting richer at everyone else’s expense. Maybe they all skipped that class?

I do see a decent amount of activity on it. Full disclaimer, I am not a security expert. I know just enough to be dangerous. But, I see at least a few connection attempts from different IPs about every day. The top 3 countries of origin are China, Russia, and Brazil (based on the reverse DNS, but it’s possible some are using VPNs to hide their origin). My impression is they’re all bots that just go through a list of IP addresses, attempting to connect to the standard ssh port, then guessing the username and password. What I’ve found is they usually go through a list of likely ssh ports until one of them connects. Having the default port open to only the honeypot means they usually establish the connection, then leave it at that, so my real ssh port never gets hit. I kinda think of it like scambaiting, where I’m just wasting time they might otherwise spend trying to break into someone else’s real ssh server.

I have https open along with a non-standard port for ssh. Just for fun, I have the standard ssh port open, but redirecting to a Raspberry Pi running a honeypot. It’s fun to mess with foreign bots trying to access my network.

Could also have been one of the devs who leaked it. Lots of us keep copies of the source for stuff we work on, so they may have figured it’s been long enough that no one would care if it leaked. However, I haven’t looked at it yet, but I imagine it would be most problematic legally if it contained proprietary 3rd party code. Leaking that could land someone in hot water.