On Tue, Apr 14, 2015 at 8:32 AM, Eric Shepherd <esheph...@mozilla.com> wrote:
> Joshua Cranmer [image: 🐧] wrote: > >> If you actually go to read the details of the proposal rather than >> relying only on the headline, you'd find that there is an intent to >> actually let you continue to use http for, e.g., localhost. The exact >> boundary between "secure" HTTP and "insecure" HTTP is being actively >> discussed in other forums. >> > My main concern with the notion of phasing out unsecured HTTP is that > doing so will cripple or eliminate Internet access by older devices that > aren't generally capable of handling encryption and decryption on such a > massive scale in real time. > > While it may sound silly, those of us who are intro classic computers and > making them do fun new things use HTTP to connect 10 MHz (or even 1 MHz) > machines to the Internet. These machines can't handle the demands of SSL. > So this is a step toward making their Internet connections go away. > > This may not be enough of a reason to save HTTP, but it's something I > wanted to point out. As the owner of a Mac SE/30 with an 100MB Ethernet card, I sympathize. However, consider it part of the challenge! :) There are definitely TLS stacks that work on some pretty small devices. --Richard > > > -- > > Eric Shepherd > Senior Technical Writer > Mozilla <https://www.mozilla.org/> > Blog: http://www.bitstampede.com/ > Twitter: http://twitter.com/sheppy > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
