Earlier quoted context omitted.
> I'd rather expose a Wireguard port and control my keys than introduce a third party like Tailscale. Ideal if you have the resources (time, money, expertise). There are different levels of qualifications, convenience, and trust that shape what people can and will deploy. This defines where you draw the line - at owning every binary of every service you use, at compiling the binaries yourself, at checking the code th…
> It's simple, you increase your attack surface, and the effort and expertise needed to mitigate that. Sure, but opening up one port is a much smaller surface than exposing yourself to a whole cloud hosting company.
CLI agents make self-hosting on a home server easier and fun
531–540 of 570 posts
Re: CLI agents make self-hosting on a home server easier and fun
#532Earlier quoted context omitted.
The point of massive fines, and in some cases jailtime for driving without a license is control. If someone breaks regs, you want to be able to levy fines or jail. If they do it a lot, you want an inability to drive at all. It's about regulating poor drivers. And yes, initially vetting a driver too.
I don't really know any adults who don't drive, and nobody ever told me they weren't capable. I don't think it's about driving ability, besides the initial vetting.
Re: CLI agents make self-hosting on a home server easier and fun
#533Earlier quoted context omitted.
I'd rather expose a Wireguard port and control my keys than introduce a third party like Tailscale. I am not sure why people are so afraid of exposing ports. I have dozens of ports open on my server including SMTP, IMAP(S), HTTP(S), various game servers and don't see a problem with that. I can't rule out a vulnerability somewhere but services are containerized and/or run as separate UNIX users. It's the way the Inter…
"I'd rather expose a Wireguard port and control my keys than introduce a third party like Tailscale." It's always perplexing to me how HN commenters replying to a comment with a statement like this, e.g., something like "I prefer [choice with some degree of DIY]", will try to "argue" against it The "arguments" are rarely, "I think that is a poor choice because [list of valid reasons]" Instead the responses are someth…
Re: CLI agents make self-hosting on a home server easier and fun
#534Earlier quoted context omitted.
> It's simple, you increase your attack surface, and the effort and expertise needed to mitigate that. Sure, but opening up one port is a much smaller surface than exposing yourself to a whole cloud hosting company.
You could also use ZeroTier and get similar capabilities without a third-party being a blocker.
Re: CLI agents make self-hosting on a home server easier and fun
#535Earlier quoted context omitted.
I'd argue that no, managing your own VPN is not a basic skill - certainly not in the realms of software engineering (more like network engineering).
WireGuard is ~10 lines of config and wg genkey. Calling that "network engineering" is a stretch. The siloing of basic infrastructure knowledge into "not my discipline" is part of the problem. Software gets deployed somewhere: understanding ports, keys, and routing at a basic level is not specialized knowledge. Honestly, if 10 lines of config is "network engineering", then the bar for software engineering has dropped…
I have done that with Tailscale, most of the time was spent waiting for it to download.
Re: CLI agents make self-hosting on a home server easier and fun
#536Earlier quoted context omitted.
In theory. In the same theory, someone would need your EC SSH key to do anything with an exposed SSH port. Practice is a separate question.
SSH is TCP though and the outside world can initiate a handshake, the point being that wireguard silently discards unauthenticated traffic - there's no way they can know the port is open for listening.
It's slow to scan due to ICMP ratelimiting, but you can parallelize.
(Sure, you can disable / firewall drop that ICMP error… but then you can do the same thing with TCP RSTs.)
Re: CLI agents make self-hosting on a home server easier and fun
#537Earlier quoted context omitted.
In theory. In the same theory, someone would need your EC SSH key to do anything with an exposed SSH port. Practice is a separate question.
Not even remotely comparable. Wireguard is explicitly designed to not allow unauthenticated users to do anything, whereas SSH is explicitly designed to allow unauthenticated users to do a whole lot of things.
I'm sorry, what?
Re: CLI agents make self-hosting on a home server easier and fun
#538This posts lists inexpensive home servers, Tailscale and Claude Code as the big unlocks. I actually think Tailscale may be an even bigger deal here than sysadmin help from Claude Code at al. The biggest reason I had not to run a home server was security: I'm worried that I might fall behind on updates and end up compromised. Tailscale dramatically reduces this risk, because I can so easily configure it so my own devi…
I'd rather expose a Wireguard port and control my keys than introduce a third party like Tailscale. I am not sure why people are so afraid of exposing ports. I have dozens of ports open on my server including SMTP, IMAP(S), HTTP(S), various game servers and don't see a problem with that. I can't rule out a vulnerability somewhere but services are containerized and/or run as separate UNIX users. It's the way the Inter…
Re: CLI agents make self-hosting on a home server easier and fun
#539Earlier quoted context omitted.
I think you answered the question. Sugar. It's easier than managing your own Wireguard connections. Adding a device just means logging into the Tailscale client, no need to distribute information to or from other devices. Get a new phone while traveling because yours was stolen? You can set up Tailscale and be back on your private network in a couple minutes. Why did people use Dropbox instead of setting up their own…
Yeah, but "people" here are alleged software engieners. It is quite disheartening.
Full stack is for start ups and small projects.
Re: CLI agents make self-hosting on a home server easier and fun
#540Earlier quoted context omitted.
My spouse and I work at home and after the first couple multi-day power outages we invested in good UPSs and a whole house standby generator. Now when the power goes out it's down for at most 30 seconds. This also makes self-hosting more viable, since our availability is constrained by internet provider rather than power.
Yeah we did a similar thing. Same situation, spouse and I both work from home, and we got hit by a multiple day power outage due to a rare severe ice storm. So now I have an EV and a transfer switch so I can go for a week without power, and I have a Starlink upstream connection in standby mode that can be activated in minutes. Of course that means we’ll not have another ice storm in my lifetime. My neighbors should t…