Serveo: Expose Local Servers to the Internet
61–70 of 122 posts
Re: Serveo: Expose Local Servers to the Internet
#62How could that be useful in Serveo? How else could SSH be used creatively?
Re: Serveo: Expose Local Servers to the Internet
#63Earlier quoted context omitted.
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…
for the dot coms, let's not forget about Google's rank incentive.
https://thenextweb.com/google/2015/12/17/unsecured-websites-...
Re: Serveo: Expose Local Servers to the Internet
#64Earlier quoted context omitted.
> By rewriting the IP headers of packets as they traverse routing devices. How does that prevent hosts on that other network from accessing hosts on your "private network"? Like, a packet addressed to one of the hosts on your "private network" arrives at your NAT gateway from the "other network". How does the NAT rewrite the IP headers, and how does that provide access control? > If you’re trying to say that all NAT…
Because without NAT, none of the devices on my home network would be able to connect to any internet connected hosts. That is, unless I assigned internet routable addresses to their network interfaces. If I did that, I’d either have to install firewalls on my devices, or expose all services running on my devices to the internet. But I don’t have to do that, because my home router uses NAT to allow all devices on my h…
Your router could still firewall them all the same. NAT or no NAT. You would not need to have a firewall on each individual device.
Re: Serveo: Expose Local Servers to the Internet
#65Earlier quoted context omitted.
Because without NAT, none of the devices on my home network would be able to connect to any internet connected hosts. That is, unless I assigned internet routable addresses to their network interfaces. If I did that, I’d either have to install firewalls on my devices, or expose all services running on my devices to the internet. But I don’t have to do that, because my home router uses NAT to allow all devices on my h…
> If I did that, I’d either have to install firewalls on my devices, or expose all services running on my devices to the internet. Your router could still firewall them all the same. NAT or no NAT. You would not need to have a firewall on each individual device.
Re: Serveo: Expose Local Servers to the Internet
#66NAT 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.
Nearly 40% of US traffic is already IPv6. 40% in Germany, 30% in Japan. I haven't heard of any massive increase in security issues caused by every device getting its own IP address.
Re: Serveo: Expose Local Servers to the Internet
#67Earlier 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.
> 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. Nearly 40% of US traffic is already IPv6. 40% in Germany, 30% in Japan. I haven't heard of any massive increase in security issues caused by every device getting its own IP address.
Re: Serveo: Expose Local Servers to the Internet
#68Earlier quoted context omitted.
> If I did that, I’d either have to install firewalls on my devices, or expose all services running on my devices to the internet. Your router could still firewall them all the same. NAT or no NAT. You would not need to have a firewall on each individual device.
So you can replace the security controls provided by NAT with security controls provided by a firewall. How does this support the argument that NAT doesn’t provide any security controls?
That's something you can circumvent in certain scenarios. The technique is called "NAT hole punching".
Re: Serveo: Expose Local Servers to the Internet
#69Earlier quoted context omitted.
> 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. Nearly 40% of US traffic is already IPv6. 40% in Germany, 30% in Japan. I haven't heard of any massive increase in security issues caused by every device getting its own IP address.
Is that because there's still usually NAT at the users router or cell tower even with IPv6?
Re: Serveo: Expose Local Servers to the Internet
#70Curious, what was this written in?