Live data from Hacker News

Serveo: Expose Local Servers to the Internet

serveo.net

21–30 of 122 posts

Re: Serveo: Expose Local Servers to the Internet

#21
post #14
post #4

I've been using ngrok for development purposes. This seems like an interesting alternative.

Agreed. In particular when testing any sort of web hooks/callbacks, I get pretty sick of constantly updating configurations as the ngrok tunnels change subdomain. Self-hosting is also a nice option.

The paid ngrok options are pretty sweet though and solve these issues.

Re: Serveo: Expose Local Servers to the Internet

#22

NAT has crippled the Internet. We are permanently dependent on public facing servers to route packets from one device to the other. This service is absolutely not needed in a non-NAT world. And I strongly believe we have lost a lot by being completely dependent on client-server model of Internet. I've written more about it here https://www.ankshilp.in/post/the_broken_promise_of_internet/

I honestly think the fault here is not technical, it's ISPs.

Between the RIAA/MPAA breathing down their necks about piracy, and the realization they could make a mint charging inflated "business rates" than letting you do what you wanted with your own damn internet connection, shit got locked up tight so fast no one even noticed.

It's not NAT that's why my ISP is blocking half the protocols on the Internet. Why every ISP I've had for the last decade has blocked outgoing HTTP. Why I'd need to us a fucking VPN tunnel just to get SSH to my home computer. It's greed.

It's the forgotten front of the net neutrality fight, and it's gone almost entirely ignored. We don't have the right to our own outgoing traffic anymore, and this has been the case for far longer than IP allocation has been an issue.

Re: Serveo: Expose Local Servers to the Internet

#23
post #21
post #14

Earlier quoted context omitted.

Agreed. In particular when testing any sort of web hooks/callbacks, I get pretty sick of constantly updating configurations as the ngrok tunnels change subdomain. Self-hosting is also a nice option.

The paid ngrok options are pretty sweet though and solve these issues.

Seriously. ngrok is underpriced - I would pay double the ask without even flinching. I can't even count how many times it has actively aided in me getting paid.

Re: Serveo: Expose Local Servers to the Internet

#24
post #13

NAT has crippled the Internet. We are permanently dependent on public facing servers to route packets from one device to the other. This service is absolutely not needed in a non-NAT world. And I strongly believe we have lost a lot by being completely dependent on client-server model of Internet. I've written more about it here https://www.ankshilp.in/post/the_broken_promise_of_internet/

I'm probably missing something, but I think that, for home networks at least, NAT is wonderful because of how it requires some effort to make devices exposed on the external network. If we were given an unlimited supply of IP addresses from the ISP and all devices were accessible externally, it seems security issues in would be a much larger problem.

NAT is definitively not a security layer and was never intended as such. You can get better security with a simple stateful ingress firewall (block packets not associated with an established/related connection) which is what most people think of for security with NAT.

The only slight benefit it has imparted is the privacy benefit of hiding multiple devices behind a single address, but they can usually be individually profile anyway.

Re: Serveo: Expose Local Servers to the Internet

#25
post #18
post #9

Earlier quoted context omitted.

Fortunately we're being uncrippled again by the continued deployment of IPv6 [0]. [0]: https://www.google.com/intl/en/ipv6/statistics.html

Germany (44%) and Belgium (53%) are killing it! The biggest surprise is India matching the US, must be that Indian mobile company that people mentioned here the other day? I'd love to see similar graphs for TLS. Edit: Google shows it only for Chromium sampling but it's nearly 90% in most countries which is almost double what it was before the Snowden leaks: https://transparencyreport.google.com/https/overview

Honestly I think the adoption of TLS has more to do with free certificates from LetsEncrypt and CloudFlare than the Snowden leaks.

As much as I'd like to think people were concerned about the privacy of their communications... I don't think most of the masses actually care about security or avoid conveniences based on threats to their privacy...

Re: Serveo: Expose Local Servers to the Internet

#26
post #13

Earlier quoted context omitted.

I'm probably missing something, but I think that, for home networks at least, NAT is wonderful because of how it requires some effort to make devices exposed on the external network. If we were given an unlimited supply of IP addresses from the ISP and all devices were accessible externally, it seems security issues in would be a much larger problem.

NAT is definitively not a security layer and was never intended as such. You can get better security with a simple stateful ingress firewall (block packets not associated with an established/related connection) which is what most people think of for security with NAT. The only slight benefit it has imparted is the privacy benefit of hiding multiple devices behind a single address, but they can usually be individually…

I've heard before that "NAT is not intended as security", but isn't the effect still the same, that an external device can't connect to a device behind NAT without explicit configuration allowing it?

Re: Serveo: Expose Local Servers to the Internet

#27
post #26

Earlier quoted context omitted.

NAT is definitively not a security layer and was never intended as such. You can get better security with a simple stateful ingress firewall (block packets not associated with an established/related connection) which is what most people think of for security with NAT. The only slight benefit it has imparted is the privacy benefit of hiding multiple devices behind a single address, but they can usually be individually…

I've heard before that "NAT is not intended as security", but isn't the effect still the same, that an external device can't connect to a device behind NAT without explicit configuration allowing it?

That is generally true, but has weird edge cases. For example using not so specially crafted ICMP packets[1] two hosts each behind independent NATs can communicate with each other without any change to a firewall configuration.

Also honorable mentions: The UPnP protocol & STUN servers

[1]: https://samy.pl/chownat/

Re: Serveo: Expose Local Servers to the Internet

#28
post #18

Earlier quoted context omitted.

Germany (44%) and Belgium (53%) are killing it! The biggest surprise is India matching the US, must be that Indian mobile company that people mentioned here the other day? I'd love to see similar graphs for TLS. Edit: Google shows it only for Chromium sampling but it's nearly 90% in most countries which is almost double what it was before the Snowden leaks: https://transparencyreport.google.com/https/overview

Honestly I think the adoption of TLS has more to do with free certificates from LetsEncrypt and CloudFlare than the Snowden leaks. As much as I'd like to think people were concerned about the privacy of their communications... I don't think most of the masses actually care about security or avoid conveniences based on threats to their privacy...

“The masses” don’t deploy http servers. They don’t need to implement tls. The fact is that something struck a nerve and motivated the people who handle this to implement TLS. Whether that’s tech-minded understanding or consumer-fomented demand channeled through CTOs, I don’t really care. Let’s Encrypt founders didn’t sit down one day with a master business plan of getting rich off free certs. I wouldn’t be the least bit surprised if a high-level view showed Snowden having a lot to do with it.

Re: Serveo: Expose Local Servers to the Internet

#29

NAT has crippled the Internet. We are permanently dependent on public facing servers to route packets from one device to the other. This service is absolutely not needed in a non-NAT world. And I strongly believe we have lost a lot by being completely dependent on client-server model of Internet. I've written more about it here https://www.ankshilp.in/post/the_broken_promise_of_internet/

Buckle up because it'll be a while before ipv6 gets mass adoption and folks will need to support v4 long after that.

I remember (upon mentioning my excitement regarding IPv6) this exact sentiment over a decade ago. It was accurate then, and it’s accurate now.
Post reply on HN