NeverSSL • Hacker News Board

Re: NeverSSL

#71

Post by artursapek » Sat, Nov 02, 2019, 11:12 PM UTC

hk__2 wrote: post #66

http://neverssl.com/changes > I also want to keep neverssl.com ad free, but as it's now costing me about $2,000 a year to host it, […] Wait, how could hosting a static website cost $2k/year?!

Bandwidth, maybe? That page is 53.8 KB total. $2k does seem high though.

Re: NeverSSL

#72

Post by lucb1e » Sat, Nov 02, 2019, 11:13 PM UTC

riffic wrote: post #56

http://example.com is my captive portal triggering website go-to. IANA reserved and will be there when I need it forever .

They might not run a web service indefinitely, nor did anyone ever say they'll not redirect to https. It happens to work just like a random other 90s website might work.

Re: NeverSSL

#73

Post by ape4 » Sat, Nov 02, 2019, 11:13 PM UTC

hk__2 wrote: post #66

http://neverssl.com/changes > I also want to keep neverssl.com ad free, but as it's now costing me about $2,000 a year to host it, […] Wait, how could hosting a static website cost $2k/year?!

With no graphics

Re: NeverSSL

#74

Post by tialaramex » Sat, Nov 02, 2019, 11:15 PM UTC

JoshTriplett wrote: post #54

cwyers wrote: post #38

So, sites like this are useful. (It's certainly better than memorizing the URL that various hotels use for their wifi portals, which I have done before, sadly.) But is there anybody working on solving this problem transparently to the end user? It seems user-hostile to require people to remember a non-HTTPS URL, especially as more and more sites move.

> But is there anybody working on solving this problem transparently to the end user? Yes. RFC 7710 defines a DHCP option to supply a URI for a captive portal page. https://tools.ietf.org/html/rfc7710

And if you think there are things that need doing beyond RFC7710 (you would be correct) the place to go help/ bring your ideas is the IETF's capport (Captive Portal Interaction) Working Group: https://datatracker.ietf.org/wg/capport/about/

Re: NeverSSL

#75

Post by lucb1e » Sat, Nov 02, 2019, 11:16 PM UTC

kaycebasques wrote: post #61

When I’m having trouble logging into a Wi-Fi network I just go to 128.1.1.1. Seems to work every time.

I always used my own IP until I got to a portal that didn't work with that. Now I use a subdomain of my site. Then one very smart captive portal "moved permanently"'d that and my browser cached it, as it should, and on the next WiFi it tried to load the old one's captive portal x_x. Not sure what the solution is for that, it would happen with neverssl or any of the alternative domains mentioned here as well. I guess you'd have to manually type a random subdomain of neverssl or so.

Re: NeverSSL

#76

Post by profmonocle » Sat, Nov 02, 2019, 11:16 PM UTC

crazysim wrote: post #39

etskinner wrote: post #6

http://example.com also does this, albeit without the promise of never switching

I think the only promise example.com has is that the domain will always exist.

I'm not sure that's even true. RFC 6761 says "IANA currently maintains a web server providing a web page explaining the purpose of example domains."

Saying "currently" implies it's not guaranteed to always be true. (Although it's more likely to stick around than a random domain registered by a hobbyist.)

Re: NeverSSL

#77

Post by lima » Sat, Nov 02, 2019, 11:16 PM UTC

Evanbenn wrote: post #70

hk__2 wrote: post #66

http://neverssl.com/changes > I also want to keep neverssl.com ad free, but as it's now costing me about $2,000 a year to host it, […] Wait, how could hosting a static website cost $2k/year?!

right! they need to set up a cloudflare proxy, or have github host it for example.

Can't do any useful caching for a purposefully cache-busting website

Re: NeverSSL

#78

Post by lima » Sat, Nov 02, 2019, 11:17 PM UTC

st3fan wrote: post #63

I just use http://captive.apple.com

That upgrades to SSL for me

Re: NeverSSL

#79

Post by judge2020 » Sat, Nov 02, 2019, 11:19 PM UTC

purerandomness wrote: post #58

Typing 1.1.1.1 (Cloudflare DNS) or 8.8.8.8 (Google DNS) into the address bar does the same job, is quicker, can be easily remembered, and is safer.

1.1.1.1 might be HSTS preloaded in the future (although not in the near future - there were issues with captive portals[0])

0: https://chromium.googlesource.com/chromium/src.git/+/36b8980...

Re: NeverSSL

#80

Post by hn_throwaway_99 » Sat, Nov 02, 2019, 11:19 PM UTC

Evanbenn wrote: post #70

hk__2 wrote: post #66

http://neverssl.com/changes > I also want to keep neverssl.com ad free, but as it's now costing me about $2,000 a year to host it, […] Wait, how could hosting a static website cost $2k/year?!

right! they need to set up a cloudflare proxy, or have github host it for example.

I'm pretty sure GitHub would require SSL, no?