| Summary: | support a more strict SSL option with certificates | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Joakim Erdfelt <joakim.erdfelt> |
| Component: | other | Assignee: | Michael Gorovoy <mgorovoy> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | jesse.mcconnell, jetty-inbox, mgorovoy |
| Version: | 7.1.0 | ||
| Target Milestone: | 7.3.x | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Joakim Erdfelt
along the same lines an option to force validation of the certificates being used for a given ssl connector wouldn't be a terrible idea either... ie, you are unable to start the server if the certificate chain of the cert your starting with doesn't check out The old example of a revoked certificate is no longer valid. Need to find (or better yet mock up in a unit test) a revoked SSL certificate. making this a touch broader scope to include the server side changes as well Committed r2748, r2795, r2799, r2801, r2832 |