Back to bug 1305993
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Matthew Harmsen | 2016-02-09 18:34:04 UTC | Assignee | mharmsen | ftweedal |
| Ann Marie Rubin | 2016-02-09 22:07:45 UTC | CC | arubin | |
| Matthew Harmsen | 2016-04-21 16:09:55 UTC | Target Release | --- | 7.3 |
| Nathan Kinder | 2016-06-15 18:14:34 UTC | CC | nkinder | |
| Matthew Harmsen | 2016-06-15 18:46:34 UTC | Target Release | 7.3 | 7.4 |
| Nathan Kinder | 2016-12-01 18:50:23 UTC | Priority | unspecified | medium |
| Michal Hlavinka | 2017-01-09 16:57:36 UTC | Doc Type | Bug Fix | If docs needed, set a value |
| Siddharth Nagar | 2017-02-08 17:28:12 UTC | Priority | medium | high |
| Matthew Harmsen | 2017-03-03 18:31:34 UTC | Status | NEW | POST |
| Jaroslav Reznik | 2017-03-06 13:42:34 UTC | Blocks | 1429492 | |
| Jaroslav Reznik | 2017-03-06 13:43:02 UTC | Keywords | ZStream | |
| Matthew Harmsen | 2017-03-15 07:32:32 UTC | Status | POST | MODIFIED |
| Fixed In Version | pki-core-10.4.0-1.el7 | |||
| errata-xmlrpc | 2017-03-15 07:43:42 UTC | Status | MODIFIED | ON_QA |
| Petr Bokoc | 2017-04-03 10:53:31 UTC | CC | pbokoc | |
| Doc Text | * Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the "CommonNameToSANDefault", which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. | |||
| Geetika Kapoor | 2017-05-11 12:15:27 UTC | CC | ftweedal, gkapoor | |
| Flags | needinfo?(ftweedal) | |||
| Fraser Tweedale | 2017-05-12 04:08:35 UTC | Flags | needinfo?(ftweedal) | |
| Geetika Kapoor | 2017-05-16 05:42:37 UTC | Status | ON_QA | VERIFIED |
| Petr Bokoc | 2017-07-24 09:50:39 UTC | Doc Text | * Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the "CommonNameToSANDefault", which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. | Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the "CommonNameToSANDefault", which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. |
| Doc Type | If docs needed, set a value | Enhancement | ||
| Petr Bokoc | 2017-07-25 15:01:45 UTC | Docs Contact | pbokoc | |
| Doc Text | Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the "CommonNameToSANDefault", which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. | Added an option to copy certificate Subject Common Name to the Subject Alternative Name extension Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the `CommonNameToSANDefault` option, which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. |
||
| Fraser Tweedale | 2017-07-25 23:48:20 UTC | Doc Text | Added an option to copy certificate Subject Common Name to the Subject Alternative Name extension Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the `CommonNameToSANDefault` option, which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. | Added a profile component to copy certificate Subject Common Name to the Subject Alternative Name extension Some TLS libraries now warn or refuse to validate DNS names when the DNS name only appears in the Subject Common Name (CN) field, which is a practice that was deprecated by RFC 2818. This update adds the `CommonNameToSANDefault` profile component, which copies the Subject Common Name to the Subject Alternative Name (SAN) extension, and ensures that certificates are compliant with current standards. |
| errata-xmlrpc | 2017-08-01 22:46:01 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 18:46:01 UTC | |||
| Mike Kelly | 2018-01-19 19:28:46 UTC | CC | pioto | |
| Dinesh Prasanth | 2020-10-04 21:03:18 UTC | Link ID | Github dogtagpki/pki/issues/2269 |
Back to bug 1305993