Yeah, but you'd need to own a public domain and use it for your LAN, no? Or would it be possible to get a letsencrypt certificate for example.local
?
PlexSheep
I mean, if the server is running in a host you control, you can do whatever with it, no? You can just modify the software to just not do what other servers say, no?
Yes this is right. There may be confusion happening with binary and metric prefixes.
For example:
Kibbibyte (1024 bytes) vs Kilobyte (1000 bytes).
Yeah of course, that's what I'm doing anyways, but the purpose of a firewall would be defense in depth, even is something were to be published, the firewall got it.
You're right and it is a real problem. But consider that the EU is a huge contributor to the stability of Europe, and the world as a whole. War between EU member states is unthinkable, that wasn't the case 80 years ago.
I can configure the containers in ways that don't require ports to be published for the real network, but that's always possible. It would still be nice to have a firewall that can block even those containers that try to publish their ports to the whole (real) network.
They are Only in my docker bridge networks and have a few published ports
For my homelab, and I'll only host OSS
People in red Teams are white hats. The terms describe different things. The "color wheel" is operational and thinks in the context of an organization. Red Team tries to attack our stuff, blue team tries to defend our stuff, yellow team builds our stuff etc.
White hat is just a term for ethical hackers, black hat is a term for criminals. Grey hat means someone in-between (think political hacker defacing website of organization they don't like), there is also some more but the shades of grey are most important.
Interesting, I might have to read up on that next time. Thanks
They make money with people looking for dates, not with people having found them.