There's no need, but if you really want to, you can do it through Tailscale - Provision TLS certificates for your internal Tailscale services
HTTPS performs two duties.
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.
It does though doesn't it? since every device needs to be authorized by me first
It can still have issues with potential attacks that would redirect your client to a system outside of the VPN. It would prevent MitM but not complete replacement.
Yep! It all comes down to your attack surface and how paranoid you want to be.
How do you know you're connecting to the server you think you're connecting to? When you enter http://myserver.local into a web browser, for example, it does a DNS lookup to get an IP address. You're assuming that that lookup returns the value you think it should. BUT if something has poisoned your DNS cache, added an entry to /etc/hosts, etc. that IP address could be some other server. Without a certificate being presented by the server you likely wouldn't notice.
But as I said - it's pretty unlikely in your scenario. But something to understand better for other scenarios.
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.
I have a router with dd-wrt and I have VLANS where only my "trusted" devices are and another for everything else (like smart things or guests)
But I get your point, thank you!
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]
Good bot.
Pretty sure all men got pushed out of the middle by grimy angry goblins that steal your cookies and tokens.
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!