This blog is specifically for websites that are public facing. Sure, you can wireguard into your local network, but you can also SSH into your local network. Either way you have to poke a hole.
This blog is specifically for websites that are public facing. Sure, you can wireguard into your local network, but you can also SSH into your local network. Either way you have to poke a hole.
Good read.
I would just like to add some additional information that favors changing your SSH port to something other than the default. When crawlers are going around the internet looking for vulnerable SSH servers, they’re more than likely going to have an IP range and specifically look for port 22.
Now can they go through and scan your IP and all of its ports to look for the SSH service? Yes. But you will statistically have less interactions with bad actors this way since they might specifically be looking for port 22.
You must be one of those self-driven, motivated, and energetic developers
How do you figure this out scientifically?
Not if they tear it down and rebuild it appropriately
deleted by creator
Its up to your distros package maintainer to make the patched version available. You can find who maintains it and contact them so they are aware.
c/lostlemmies
Took me a sec to realize what you meant by this lol