Opened 16 years ago
Last modified 16 years ago
#48 closed defect
Certificates on *.scripts.mit.edu — at Initial Version
| Reported by: | andersk | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | web | Keywords: | |
| Cc: |
Description
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 mod_ssl 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.
