There's no need, but if you really want to, you can do it through Tailscale - Provision TLS certificates for your internal Tailscale services
post
HTTPS performs two duties.
- Secures your connection from prying eyes.
- Verifies the identity of the server.
Your VPN provides the former but not the latter. That said the odds of there being an issue in this regard are so slim as to be zero, so you'll probably be fine.
replies:
Do you have any devices on your local network where the firmware hasn't been updated in the last 12 month? The answer to that is surprisingly frequently yes, because "smart device" companies are laughably bad about device security. My intercom runs some ancient Linux kernel, my frigging washing machine could be connected to WiFi and the box that controls my roller shutters hasn't gotten an update sind 2018.
Not everyone has those and one could isolate those in VLANs and use other measures, but in this day and age "my local home network is 100% secure" is far from a safe assumption.
Heck, even your router might be vulnerable...
Adding HTTPS is just another layer in your defense in depth. How many layers you are willing to put up with is up to you, but it's definitely not overkill.
replies:
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| HTTP | Hypertext Transfer Protocol, the Web |
| HTTPS | HTTP over SSL |
| SSL | Secure Sockets Layer, for transparent encryption |
| TLS | Transport Layer Security, supersedes SSL |
| VPN | Virtual Private Network |
3 acronyms in this thread; the most compressed thread commented on today has 8 acronyms.
[Thread #490 for this sub, first seen 5th Feb 2024, 20:05] [FAQ] [Full list] [Contact] [Source code]
replies:
Pretty sure all men got pushed out of the middle by grimy angry goblins that steal your cookies and tokens.
[deleted]
replies:
[deleted]
all 14 comments