Perhyte

Somehow my .gitconfig seems to have grown by about 20 lines after reading this article. How mysterious...

If this is something you run into often, it's likely still only for a limited number of servers? ssh and scp both respect .ssh/config, and I suspect (but haven't tested) that sftp does too. If you add something like this to that file:

Host host1 host2
  Port 8080

then SSH connections to hosts named in that first line will use port 8080 by default and you can leave off the -p/-P when contacting those hosts. You can add multiple such sections if you have other hosts that require different ports, of course.

Aurora is no longer maintained, but it still works just fine. It's a Windows app, so not web-accessible or anything, but it's free. It only contains the SRD content by default (probably for legal reasons), but there's at least one publicly-accessible elements repository for it that you can find using your favorite search engine.

Assuming they went to signed 64-bit time, it should be about 3:28:32 pm UTC on Sunday, December 4, 292277026596. Yes, that last number is a year.

This one isn't linked from the megathread?

If they have the root access typically needed to reboot a server^1^ they could also just wipe the logs without rebooting.

^1^: GUIs typically have a way to reboot without such privileges, but those are typically not installed on machines just used as servers.

... or it might incentivize more employees to cover up those illegal things happening because they don't want to get fired.

[email protected] - no posts yet though.

Why not both?

After all, I suspect neither Klingons nor Ferengi would enjoy hanging out together for eternity.

That domain currently hosts a "this domain may be for sale" page, but it's been registered since 2005 so it's definitely not because of this post.

Not to mention all the genocide.

In fact, unless you post your domain somewhere online or its registration is available somewhere, it’s unlikely anyone will ever visit your server without a direct link provided by you or someone else who knows it.

If you use HTTPS with a publicly-trusted certificate (such as via Let's Encrypt), the host names in the certificate will be published in certificate transparency logs. So at least the "main" domain will be known, as well as any subdomains you don't hide by using wildcards.

I'm not sure whether anyone uses those as a list of sites to automatically visit, but I certainly would not count on nobody doing so.

That just gives them the domain name though, so URLS with long randomly-generated paths should still be safe.