4 ms·
Yes, it works with their official packages, at least. Just updated today. Here is the basic config I'm using with it: listen x.x.x.x:
by bungle 13y ago
Yes, it works with their official packages, at least. Just updated today.
Here is the basic config I'm using with it:
listen x.x.x.x:443 default_server deferred spdy;
listen [x:x:x:x::x]:443 default_server deferred spdy ipv6only=on;
spdy_headers_comp 7;
ssl on;
ssl_certificate /etc/ssl/private/x.crt;
ssl_certificate_key /etc/ssl/private/x.key;
ssl_trusted_certificate /etc/ssl/private/x.trust;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS;
ssl_prefer_server_ciphers on;
ssl_stapling on;
ssl_stapling_verify on;
resolver 8.8.8.8 x.x.x.x
add_header Strict-Transport-Security "max-age=15768000; includeSubDomains";
add_header X-Frame-Options DENY;
add_header Alternate-Protocol 443:npn-spdy/3;
- nly 13y agoAny specific reason why you went for an STS timeout of 6 months?
- pixl97 13y agoSSL Labs test will not give you a A+ rating if it is not set at least that long. HSTS headers should always be set for a long period of time to avoid a client that only rarely connects to a site having a MITM attack occur.
- nodesocket 13y agoWhat does the following header do? add_header Alternate-Protocol 443:npn-spdy/3; Also, what exactly does deferred do on the listen directive?
- conductor 13y agoThis is from the section 3.3.1 of SPDY Protocol - Draft 2 [0]: "When a server receives a non-SPDY request which could have been served via SPDY, it should append a Alternate-Protocol header into the response stream. Note that it is valid to have multiple Alternate-Protocols headers. The field-value can also be specified as a comma-separated list, as per RFC2616 section 4.2." And you can read about "deferred" here: https://stackoverflow.com/questions/8449058/what-does-the-deferred-option-mean-in-nginxs-listen-directive https://stackoverflow.com/questions/8449058/what-does-the-de... [0] - http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft2 http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-dra...
- elithrar 13y ago> And you can read about "deferred" here: https://stackoverflow.com/questions/8449058/what-does-the-deferred-option-mean-in-nginxs-listen-directive https://stackoverflow.com/questions/8449058/what-does-the-de... Thanks for the link; I'm curious as to the downsides however (the article linked in the article doesn't fully cover them), and a Google search doesn't yield anything concrete (i.e. deferred on vs. off).
- BobVerg 13y ago"spdy_headers_comp 7;" looks like huge overkill. It provides about 10% better compression ratio than setting 1, but two times slower.
- nodesocket 13y agoI was wondering why by default it is 0/off. Are there issues with client/browser compatibility?
- BobVerg 13y agoIt's because of CRIME vulnerability.
- nodesocket 13y agoMore information about CRIME. http://en.wikipedia.org/wiki/CRIME_(security_exploit) http://en.wikipedia.org/wiki/CRIME_(security_exploit) For now, disabling SPDY header compression is the right approach. Security > Performance.
- hobohacker 13y agoLet's be clear that the original CRIME attack was against request header secrets. Therefore, disabling response header compression (as nginx defaults to) does not prevent that. SPDY/3.1 request header compression is a client-side choice, not server-side.
- BobVerg 13y agoCRIME attack isn't specific to request or response. If you pass secrets in response headers, then the attack can be performed against them.
- hobohacker 13y agoThat's true, which is why I was careful to say in its original form :) Since the original attack was on cookies (request headers). To my knowledge, no other SPDY server defaults response header compression to off. But yeah, if your application does pass secrets in response headers, you should be careful.