- 5 Posts
- 2 Comments
Joined 3 年前
Cake day: 2023年6月5日
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
tripple@beehaw.orgOPto/c/cybersecurity - Cybersecurity News & Discussion@lemmy.ml•Improving HTTPS on private networks
1·3 年前Yes, there’s two approaches I’m using currently. When you register a subdomain you can choose either
localhostcert.netorlocalcert.net. The former has an A record in the public DNS that points to 127.0.0.1. The latter has no public A records so you need to manage them yourself, possibly with a local DNS resolver like unbound.


–
I previously used Privacy Badger, but I block basically everything with NoScript anyway, so it was redundant. I also used HTTPS Everywhere but you can enable that in most (all?) browsers now anyway, so you don’t need an extension any longer (the highest form of success for an extension). I also previously used LastPass, but I got out before they had their security issues, and importantly changed every password when I transitioned. On work computer I have the 1password extension.