News for hackers. Stuff that matters.
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by masterleep on Friday February 03, 2012 @07:41PM (#3549766)
SPDY doesn't provide a way to proxy-cache public assets, so it's bad for places that use such caching to mitigate low bandwidth / high latency connections.
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by magicalist on Friday February 03, 2012 @08:17PM (#3549867)
which is to be expected with a TLS connection. OTOH you get to drop all the extra TCP handshakes, you get better congestion control, you get header compression, and that encrypted connection is often a really good thing.

http://bitsup.blogspot.com/2011/09/spdy-what-i-like-about-yo...

But yes, there remains no silver bullet, and you'll have to pick the right tool for the job.

Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by eggnet on Friday February 03, 2012 @10:38PM (#3550137)
Forcing the use of TLS for SPDY seems to have been intentionally crippling.
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by JoshTriplett on Saturday February 04, 2012 @10:56AM (#3551259)
Why should a new protocol offer the option to operate insecurely?

Nothing stops a proxy from handling SPDY, if the client trusts it to do so and doesn't mind getting MITMed.

Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by eggnet on Sunday February 05, 2012 @01:36AM (#3553474)
Transparent caching is part of what makes http so great. Security is relative, you can authenticate content without encrypting it, if there is nothing sensitive about the content.

The authentication can happen external to the http or spdy transaction as well.

Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by JoshTriplett on Monday February 06, 2012 @01:46PM (#3558627)
> you can authenticate content without encrypting it

True, but insecure HTTP provides neither authentication nor encryption.

> if there is nothing sensitive about the content.

Encrypting only sensitive content leaks information to observers and attackers, namely when you transmit sensitive content, and which servers you connect to when you do so. Encrypting all content eliminates that information leak.

Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by wmf on Saturday February 04, 2012 @12:48AM (#3550398)
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by yusufg on Friday February 03, 2012 @10:48PM (#3550151)
Wouldn't this be solved by sending a Cache-Control: public, max-age=<long-duration-in-seconds> header so that the assets can be stored in ISP proxy caches as well as browsers on-disk caches
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by mcpherrinm on Saturday February 04, 2012 @03:24AM (#3550621)
The problem is that ISP caches are essentially impossible with SPDY, because of mandatory TLS.
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11 by JoshTriplett on Saturday February 04, 2012 @10:58AM (#3551262)
I'd consider that a feature, not a bug. Transparent proxies considered harmful, especially when done without informing their users.

A SPDY client that trusts a particular proxy could easily allow that proxy to operate on its behalf, and SPDY would actually make that far more efficient.