• 0 Posts
  • 7 Comments
Joined 11 months ago
cake
Cake day: October 27th, 2023

help-circle



  • Anything that faces the internet I have on a separate vlan. Each system on that vlan is treated as if it was facing the internet directly, that way if one of them gets compromised the hacker will not get far trying to get into any other machines.

    Rest of my network is a little more tame just for ease of access since it’s only me on here.

    Although at some point I do want to revisit my security protocol even locally, just in case. Hitting some kind of drive by trojan script or something within the browser is always a possibility, it could work in reverse where it connects to an external server and then accesses the rest of the network that way. I’m not aware of such trojans but I’m sure it’s possible.

    I do block all outbound ports except for base internet ports but a properly written malicious script would probably take that into account and use a common port like 443.

    At some point I might setup a honeypot. Just need to name the VM “cryptowallet” or something like that and it would be a very fast target. If access to it is detected it would alert me and shut off the internet.




  • I recently did the same! I was using a bunch of individual .loc domains for all my servers and I recently moved to using a sub domain off a real domain that I own. It feels more professional because that’s how my work does it for their network. So everything is servername.int.mydomain.com. I setup Lets encrypt on my web server and I have a local rsync script that just grabs the cert off the web server. I didn’t do all of my servers yet but did the more important ones. Of course those only resolve locally since the records are local only. int.mydomain.com resolves externally as a wild card and just goes to a common page that does nothing but it allows for Lets Encrypt validation to work.

    Firefox has this annoying thing where it warns you about unsecured passwords in forms and I was really getting irritated by that on my local dev server because it does like a drop down thing that gets in the way of the rest of the form.

    For now I’m just specifying each sub domain to LE, but I eventually want to setup the zone as dynamic and do a wildcard, which requires to do a txt record or something… it’s a bit more involved so didn’t look at it yet.

    I also discovered the DHCP option “search domain”. Seen it before but never really knew what it was. Well you can specify your subdomain in there so that on any workstation getting DHCP you can time servername and it will auto complete the .sub.domain.tld part. I guess this is how windows 98 Netbios used to work. I just never really put the two and two together.