Bug #75387 | Support CRL Distribution Points and/or OCSP | ||
---|---|---|---|
Submitted: | 1 Jan 2015 15:17 | Modified: | 12 Jan 2017 8:14 |
Reporter: | Daniël van Eeden (OCA) | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Security: Encryption | Severity: | S4 (Feature request) |
Version: | 5.6.22 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | cdp, crl, OCSP, revocation, revoke, SSL, tls |
[1 Jan 2015 15:17]
Daniël van Eeden
[1 Jan 2015 15:51]
Daniël van Eeden
CRL's for browsers/internet is not really working (they became quite big after Heartbleed and are not checked often by browsers). But CRL's for an internal CA might work fine, but distributing the CRL is hard. A CDP would help here. Another solution to revoke certificates is OCSP, but setting up an OCSP responder is complicated. This is one of the only solutions which could work with MySQL when using public CA's. I don't think MySQL supports OCSP yet. There is yet another solution: CRLsets, but that's browser only and proprietary. So the options now are: - Distibuting a CRL for all servers and clients (although Workbench can't use a CRL) - Replacing the CA and all certificates when one or more certificates must be revoked - Using short lived certificates and then not revoking them but just let them expire. But without some fully automatic certificate rollover this is quite a lot of work
[1 Jan 2015 15:51]
Daniël van Eeden
Add more tags
[1 Jan 2015 15:52]
Daniël van Eeden
change the title
[12 Jan 2017 8:14]
MySQL Verification Team
Hello Daniël, Thank you for the feature request! Thanks, Umesh