Custom Query (196 matches)

Most of our autoinstallers, in particular Wordpress, break when accessed from a URL that they weren't originally installed at. We should fix them.

Currently lockername.scripts.mit.edu gives a certificate error. We have a valid certificate for *.scripts.mit.edu but it is currently not used. The problem is that (modulo recent extensions) the HTTPS protocol doesn’t support sending the virtual host name before the server must decide which certificate to present.

There have been two proposed solutions. One is to use the ​SNI extension. This requires upgrading OpenSSL to at least 0.9.8f, ​patching mod_ssl, and using relatively recent browsers (old browsers will fall back to the current behavior).

The other is to move *.scripts.mit.edu to a separate IP from scripts.mit.edu, so that the server knows which certificate to present based on the IP. This is less general (we can’t extend this to work with arbitrary vhosts), but we could probably implement it now.

(Split out from #48.)

Currently lockername.scripts.mit.edu gives a certificate error on IE 6 and Safari. The problem is that (modulo the recent SNI extension) the HTTPS protocol doesn’t support sending the virtual host name before the server must decide which certificate to present. In #48, Joe installed SNI, which FF 2 and IE 7 understand.

To accomplish the highly desirable #17, we need to support these other browsers; many scripts users will not consider it acceptable that their viewers on IE 6 and Safari get certificate errors. To do this, we can move scripts.mit.edu to a separate IP from *.scripts.mit.edu, so that the server knows which certificate to present based on the IP.