Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SSL considered bloated

naughtycomputer.uk

Post reply on HN
Print view View original

1–10 of 60 posts

Re: SSL considered bloated

#3

Post by liviu- »

mkj wrote: post #2

I didn't check the link, but I bet that "HTTP server in one line of code" doesn't include a TCP stack.

The "one-line" server is just multiple commands separated by ';' and joined into one line. At best a pointless exercise, and at worst a deceiving one.

Re: SSL considered bloated

#6

Post by CiPHPerCoder »

> Seems to me a bit like equipping everyone with armour to make shooting them more difficult. Solving the problem the wrong way?

I don't know, making humans immune to bullets would be an elegant solution to the gun control debate which doesn't involve disagreements over the second amendment, and would make everyone win.

Re: SSL considered bloated

#7

Post by pfg »

mkj wrote: post #2

I didn't check the link, but I bet that "HTTP server in one line of code" doesn't include a TCP stack.

Precisely - and just like that one line of code is enough to spawn a HTTP server, a different line of code could be enough to spawn a HTTPS server.

It's a matter of improving the tooling. No one is advocating to disable HTTP today, what browser vendors are trying to do is get the ecosystem to a point where that's possible without a significant increase in cost for site operators.

Similarly, HTTP/2 has been tuned specifically for (typically high-latency, low-bandwidth) mobile connections and is practically (at least) indistinguishable from the speed of (optimized) HTTP. This is only going to improve with things like Zero-RTT handshakes coming with TLS 1.3.

Re: SSL considered bloated

#8

Post by mrweasel »

mkj wrote: post #2

I didn't check the link, but I bet that "HTTP server in one line of code" doesn't include a TCP stack.

It uses Netcat, and it would be much more readable if it where more lines.

I suppose you could take some small web server, written in C, and just remove all newlines, but what's the point really.

The article seems to overlook on aspect of https. It's much easier for the site operator to just serve everything over https. We tried the whole "switch the user to https" when needed years ago. It was cumbersome and we often got it wrong and exposed traffic that was suppose to be encrypted.

The point is well made. We don't NEED https all the time. It's just easier and most of our connections and devices don't care about the overhead.

Re: SSL considered bloated

#9

Post by kraftman »

liviu- wrote: post #3
mkj wrote: post #2

I didn't check the link, but I bet that "HTTP server in one line of code" doesn't include a TCP stack.

The "one-line" server is just multiple commands separated by ';' and joined into one line. At best a pointless exercise, and at worst a deceiving one.

Did you know you can rewrite jQuery in just 4 lines of code? https://code.jquery.com/jquery-2.2.4.min.js

Re: SSL considered bloated

#10

Post by laurent123456 »

mrweasel wrote: post #8
mkj wrote: post #2

I didn't check the link, but I bet that "HTTP server in one line of code" doesn't include a TCP stack.

It uses Netcat, and it would be much more readable if it where more lines. I suppose you could take some small web server, written in C, and just remove all newlines, but what's the point really. The article seems to overlook on aspect of https. It's much easier for the site operator to just serve everything over https. We tried the whole "switch the user to https" when needed years ago. It was cumbersome and we ofte…

Anything can be done in one line when using existing tools that are made of thousands of lines. This is also a one line web server: python -m SimpleHTTPServer 8080
Post reply on HN