Oh, cool, they added that a few months ago; it only took them over 5 years to add it. I still don’t get why everybody likes it, it punishes you for building big and it has the slowest opening of all factory games I’ve ever played. I’d like to say I’d give it another try, but it runs like dog ass now, so I can’t play it anymore.

Is Satisfactory a franchise? I just don’t get it; it’s a worse Factorio. It’s poorly paced and it doesn’t have the tools you need to build big, like priority splitters.

it attempts to log in using a list of credentials.

Do you read what you post or do you just google “ssh vulnerability” and post the first result to waste my inbox space?

Software doesn’t get patched all the time,

SSH does, it is one of the codebases with the most eyeballs on it at any given time and patches to it get fast-tracked downstream.

advising hobbiests on how to configure and maintain their personal server, not the engineering meeting for a fortune 500

You don’t need to be a genius to enable keys, disable root and install fail2ban.

it remains best practice not to expose ssh to raw internet unless absolutely necessary

This is correct, but we are arguing about a case in which it is necessary to expose something and it’s better that it’s one of the most secure and battle-tested pieces of software in the world as opposed to some open source hobby *arr stack.

arguing against the industry standard … more experience and engineering time than you or I.

I work in this industry, ma’am.

Did you know that simply being connected to the internet puts you at risk? Your firewall could have a vulnerability! Your router’s admin panel could be misconfiguration and exposed to the internet! The only way to be safe is to unplug your cable and stop replying to me. Also rip out your bluetooth modules and any LEDs in every device you own because they have been demonstrated to be attack vectors. In fact just stop using anything more complicated than a MOSFET.

You did link a vulnerability! That is true. I didn’t claim SSH had a clean track record, I claimed it had a better track record than most other software. That vulnerability is hard to exploit, and generates a lot of noise if you were to try, which nobody has because it’s never been found in the wild.

People who sit on 0-days for critical software like SSH don’t go out and try to mass-exploit it because it will be found within the day and patched within the week once they start making noise. This is not a quiet exploit. If they’re smart, they sell it. If they’re ambitious, they build an elaborate multi-chain attack against a specific target. Only 0.14% of devices vulnerable to this exploit are EoL versions of OpenSSH, so once this was patched, it was no longer a useful attack vector.

It would also have been completely negated by fail2ban, which is prominently deployed on internet facing SSH, as it required thousands and thousands of connection attempts to trigger the condition. It could also have been mitigated by not running sshd as root, though I understand that most people don’t want to deal with that headache even though it is possible.

There are thousands of independent honeypots that sit quietly and sniff all the mass-attacks and they earn their daily bread by aggregating and reporting this data. If you run a mass exploit, you will be found within the day. Trust me, I burned an IP address by regularly scanning the whole IPv4 space. You are going to end up on blacklists real fuckin’ fast and whatever you were doing will be noticed and reported.

If you’re going to open something, SSH is a very safe choice. But yes, don’t open it if you don’t need it. We are discussing how to open a service to the internet safely, though, so we need it.

If you’re going to open something, SSH is far, far more battle-tested than much other software, even popular software. Pragmatically, If someone is sitting on a 0-day for SSH, do you genuinely think they’re gonna waste that on you and me? Either they’re gonna sell it to cash out as fast as possible, or they’ll sit on it while plotting an attack against someone who has real money. It is an unhealthy level of paranoia to suggest that SSH is not secure, or that it’s less secure than the hundreds of other solutions to this problem.

Here is my IP address, make me eat my words.
2a05:f6c7:8321::164 | 89.160.150.164

They can try all they like, man. They’re not gonna guess a username, key and password.

I’m going to post it again.

For anyone else looking for a reason to stay away from plebbit- uh, look at their X account https://x.com/getplebbit It’s 4chan crypto hashwash

the problem with federated social media is that each federated instance is just a regular centralized sites. They can censor each other,

Also, this is a feature. This is intentional.

Any of those can host a relay, the question is what you expect the throughput to be. I don’t expect the Zero W to survive 5 sustained Mbps, but the 4B and the ThinkPad should easily eat 20 sustained Mbps.

I am hosting a high speed relay right now, and have been for 4+ years, on my home address. I am not getting attacked beyond the usual drivebys that I’d get hit with regardless because I host other outward-facing things.

You do look suspicious to large social media sites, but besides those: I’ve never been blocked from somewhere due to my relay.

It was a parked car, there was no one in or around it.

Yes, but you are mistaken if you think your data is safe on closed platforms.
If you post it on the internet, you have to assume it’s gonna be there forever.

LibreWolf is Firefox without the bullshit.

I think life is easier if you stop managing metadata and instead deal in folder structure. My music has never had consistent metadata and tagging, yet it’s never been a problem. I use Gonic and just browse my music by folder structure.

That’s awesome; I knew I’d seen it around!

what is that little pixel cat at the top? It also appears on https://katia.ripe.net/ is it referencing something?

reposotory

It says (updated) but what is the update?

Firefox is in the same situation. Bloated umbrella org (Mozilla) that has dubious funding sources builds subpar products. Look at how much support implementing JPEG XL had, and how they just didn’t care and completely shut the conversation down when Google said no.

The Matrix foundation didn’t embrace and extend anything, as they were always in control of the spec.

EEE applies to when corporations (notably Microsoft) embraces projects that aren’t theirs and takes them under their wing, expands on functionality which attracts all the users and makes them the sole developer of that functionality, which kills the old, open forks. Microsoft then kills their version of it, and the whole thing dies.

and the backend is no longer fully open source

You have no idea how funny that is because I called it on a whim half a decade ago.