As you say, “at the time, a reasonable decision”. What I don’t understand tho, is, why nobody, for five seconds, maybe thought, how it could be a good idea to just filter this standard address at the SMTP server to be redirected to something sensible inside the org. My best guess is, different departments / sub orgs.
I enjoy apalrd very much, down to earth, deep dive, no bullshit explanatory videos mostly about networking.
I don’t know about torrent downloads, but for “obviously illegal” streaming and IPTV offerings, customers also will get bonked. For example [German]: https://www.bms-rechtsanwaelte.de/wirtschaftsrecht-blog/illegales-iptv-streaming-strafbarkeit-nutzer
Hi, could you tell me why? I mean, I think I understand the basics of the risk of brute force attacks. My mitigation for the admin account is, not to allow login outside the local network. Users are allowed from anywhere, as my family uses the library. Also my service (there are others) are routed through NGINX.
Do you have tips for external users using, for example, a VPN only for specific addresses / IPs? At least that was an idea I had, but didn’t got got around to dig for solutions.
Thanks in advance.
Angefangen habe ich mit no-ip oder so, dann duckduckdns, jetzt bei dynv6.com. Sind alle kostenlos. Der große Vorteil bei dyn6 ist, dass man nur dass Präfix (2003:1:2:3::) per Script übergeben und für Subdomains nur den Interface Identifier (::4:5:6:7) angeben muss. Daraus wird dann die ganze ipv6 gebaut (2003:1:2:3:4:5:6:7) womit sich Dienste gezielt ansprechen lassen. IPv4 geht natürlich auch.
Die Wechsel habe seinerzeit durchgeführt, weil ich immer wieder Probleme hatte, interne Dienste zu erreichen. Ursache war natürlich eigene Dummheit (Portweiterleitungen falsch).