8 ms·
Hmm question: Will this race to secure the internet mostly by applying ever more complex band aids end up in completely discouraging small entities from runnin
by nottorp 5y ago
Hmm question:
Will this race to secure the internet mostly by applying ever more complex band aids end up in completely discouraging small entities from running their own public resources?
It's already next to impossible to run a public home server. Is it likely to become completely impossible?
- MonaroVXR 5y ago>It's already next to impossible to run a public home server. Is it likely to become completely impossible? Why? I try to do this, it's an exercise that I wanted to do.
- sergiomattei 5y agoI’m curious. Are there any new major difficulties when setting up home servers? Last time I tried it was a little annoying with dynamic IPs getting in the way, but possible with just a port forward or UPnP. Are ISPs making changes to prevent this?
- southerntofu 5y agoThat's about it. In addition, some ISPs make sure you cannot change the resolver advertised on DHCP, and that your own IP is routed via the Internet and back (so local requests are slow as hell), both of which can be hacked around by running your own router behind the ISP's modem/router. Of course, the real solution to the problem is to find a decent ISP, like a non-profit from FFDN.org federation. Then you have "real" internet and no worries for selfhosting.
- nottorp 5y agoAnd how much time/expertise do you need to not trigger all kinds of warnings in modern browsers?
- space_fountain 5y agoFairly little? I think you might be thinking of email where running your own email sever is tough
- phicoh 5y agoReceiving mail is also not hard. You may have to deal with the bonus mail (spam). But that's it.
- phicoh 5y agoClose to none. Just a letsencrypt cert and not completely outdated ciphers is enough.
- nottorp 5y ago:) "Just a letsencrypt cert". That's right for me and most off the HN audience. Is it right for the general public?
- throw0101a 5y ago> Is it right for the general public? My Asus router has a checkbox for dynamic DNS and for getting Let's Encrypt certs. See Method 2: * https://www.asus.com/us/support/FAQ/1034294/#a2 https://www.asus.com/us/support/FAQ/1034294/#a2
- LinuxBender 5y agoYes. Even the most complex technical setup can be accomplished by a non-technical person that can follow directions assuming that someone took the time to write clear and concise directions and included common caveats and troubles that one may run into and where to check for them. I have proven this many times over by having managers and directors that were non-technical follow my instructions. In the rare moments this breaks down, forums and chat rooms can be a very handy gap-filler and provides an indirect feedback loop to further improve documentation.
- phicoh 5y agoYes, because if you web server publicly reachable, letencrypt can be automated easily. And there is plenty of letsencrypt software that does fully automates this. A public web server is the easy part if you want to do letsencrypt.
- vetinari 5y agoLetsencrypt is easy, if you are running generic Linux distribution and can easily install whatever you want. But you might run a device that already comes with software, and letsencrypt support is either limited (example: Synology; their implementation allows only http-01 challenge so if you need dns-01, tough luck. Even wildcards are a new feature) or non-existent (example: Ubiquiti, and their cloud keys (administration UI, guest portal) or routers (Radius/WPA Enterprise needs TLS cert too)).
- jeroenhd 5y agoI've never run into trouble running stuff from home. SMTP from home is always going to be problematic, though. The lack of IPv4 address space has started a trend of CGNAT which makes hosting from home nearly impossible. Luckily, IPv6 continues to be rolled out, but in many situations thst would lead to your services only being reachable through IPv6. There are still a great many outdated networks out there that can't reach IPv6, so you might run into trouble there. If you can get a public IPv4 IP address, I see no reason why you'd run into issues. That's more of an ISP problem than a hosting problem, in my opinion.
- dannyw 5y agomost ISPs in Australia offer a static IPv4 for a monthly fee ($5 to $10 a month).
- opk 5y agoIf you're going to pay $10 a month, you might as well pay for a VPS instead and connect up to it with wireguard, nebula or tailscale. Especially if paying means dynamic IPv4 that isn't behind CGNAT rather than an actual static IPv4 address.
- dannyw 5y agoPaying gives you a static IPv4 that remains the same for as long as you're subscribed. It's not a bad option if you're already paying for gigabit, sadly nearly impossible to get symmetrical gigabit here, but still for an extra $5 or $10 a month it's ok.
- jeroenhd 5y agoThat's an ISP problem, though. For that price it's better to just rent a VPS for hosting/proxying traffic. A wireguard tunnel to your actual home server and an nginx proxy at a $4 VPS provide more options than just a guaranteed static IP. Hell, if you can nab some capacity, you can use free VPS solutions like the one AWS and Google provide for a year, or the one Oracle providers forever if you can live with the 50mbps uplink (you get 2 servers so maybe you could tunnel that into 100mbps?) and the annoying Web UI for setting them up. Luckily, you don't need a static IP address in most use cases if you set up dyndns, as long as the IP is exclusively used by you and doesn't change too often (e.g. every week or month or so).
- smolder 5y agoIt will keep getting harder to do things independently online. The creative, individual empowerment phase of the internet is winding down. It is being gobbled up and calcified as an apparatus for rent extraction, spying and manipulation.
- hannob 5y agoI don't see how people come to this conclusion. TLS certificates used to cost a lot of money, now they're free. Pretty much all relevant web frameworks and technology stacks are published under FOSS licenses. Nothing stops you from running your own web server with either whatever is the current state of the art web tech or whatever you prefer to build yourself.
- saurik 5y agoWell, the web wasn't as encrypted before. And then when it was, the cost of the certificate wasn't a big deal in comparison to the maintenance effort of constantly rotating certificates, as you'd just buy a certificate that lasted for years and years, which isn't even allowed anymore. SSL with its massive set of "authorities" that are all granted way too broad and yet interchangeable powers with keys that both have to be rotated with pre-determined expiration dates and yet also must be shared with the client is just barely a solution to the original problem :(. But of course, the truth is that the web was never easy: it was just naive. Most (NOT ALL: some categorically only are protecting the interests of advertisers or rights holders) of these security bandaids and limitations are fixing actual problems with the web that were always there... developers just didn't know about them or didn't realize the ramifications. It would be better to have solved some of these things with solutions that are more elegant, and the lack of a definitive guide for "what all you should and should not do" sucks, but mostly the web is just banning stuff that never should have existed in the first place :(.
- opk 5y agoIt's not always possible to get certificates from Let's Encrypt for local network only services. In a big corporate environment jumping through the hoops necessary to deploy keys or get things into a DMZ can be near impossible. Even if you don't have those issues it is still one more thing to learn and setup. All these things pile up. Try setting up a basic e-mail server on the modern Internet and compare that to 20 years ago.
- bawolff 5y agoI don't see how this will make it any harder. Its not like your homeserver is likely to mix private and public ips.
- jabbany 5y agoDoesn't seem related though, since if you ran a public server from home, that server would appear through your public facing "Internet" IP rather than its intranet address. It might make some homelab setups slightly more annoying, though. FWIW, I do the same as the article for my home network: I hijack all DNS requests from intranet devices and respond with corresponding intranet IPs. Externally on the internet trying to resolve those same (sub-)domains would lead to the public facing firewall. This makes it so I can manage stuff like NASes and IoT stuff fairly easily regardless of where I'm connecting from. Luckily none of my stuff really depends on making cross-boundary requests between intranet and internet services (it's always completely internal or external) so I should still be OK.
- lqet 5y ago> next to impossible to run a public home server How so? I run a public HTTP server and a VPN server from a Raspberry Pi in my living room. It was pretty easy to set it up. Regarding the HTTP server, the only thing that was different from the last time I did this (around 2004) were SSL certificates.
- johannes1234321 5y agoWhat is the easy way to get SSL certs for my private network, which are recognized by all my browsers? My private host has no public IP or hostname, thus can't verify automatically via letsencrypt.
- rocqua 5y agoIf your host has no public IP or hostname, letsencrypt has no business issuing that host a certificate. If you wanted to, having a public facing IP that uses challenge files, and just reverse proxying that specific URL-range to the private host might work. But really, if you want SSL for a private network, self-signed certs or your own trusted CA cert is the way to go. That does mean changing your browser to accept those certs. Alternatively, drop the SSL requirement, since everything is apparently on private networks.
- wasmitnetzen 5y agoI get a *.domain.tld cert for my public server and then copy that to all my internal hosts, which are only reachable internally, but use the same domain.
- throw0101a 5y agoIf your domain registry provides an API [1] you can automated local creation of certs: * https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mode https://github.com/acmesh-official/acme.sh/wiki/DNS-alias-mo... * https://www.eff.org/deeplinks/2018/02/technical-deep-dive-securing-automation-acme-dns-challenge-validation https://www.eff.org/deeplinks/2018/02/technical-deep-dive-se... * https://dan.langille.org/2019/02/01/acme-domain-alias-mode/ https://dan.langille.org/2019/02/01/acme-domain-alias-mode/ [1] https://github.com/AnalogJ/lexicon https://github.com/AnalogJ/lexicon