Back to bug 1396985
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Tomáš Hozza | 2016-11-27 21:45:25 UTC | Keywords | Patch | |
| Priority | unspecified | medium | ||
| CC | thozza | |||
| Severity | high | medium | ||
| Paul Wouters | 2016-11-30 01:05:32 UTC | CC | nmavrogi, pwouters | |
| Tomáš Hozza | 2017-01-03 19:24:32 UTC | Keywords | FutureFeature | |
| Pavol Babinčák | 2017-04-04 08:29:46 UTC | Assignee | psimerda | pzhukov |
| Pavel Zhukov | 2017-04-10 10:52:13 UTC | Status | NEW | ASSIGNED |
| Pavel Zhukov | 2017-04-13 08:54:22 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1066603 | |
| Pavel Zhukov | 2017-07-04 11:09:37 UTC | Blocks | 1465887 | |
| Tomáš Hozza | 2017-07-24 12:38:53 UTC | Blocks | 1465928 | |
| Tomáš Hozza | 2017-08-15 11:12:23 UTC | CC | jstodola | |
| Flags | needinfo?(jstodola) | |||
| Jan Stodola | 2017-08-15 11:55:55 UTC | Flags | needinfo?(jstodola) | |
| Tomáš Hozza | 2017-08-15 12:14:39 UTC | Doc Type | If docs needed, set a value | Release Note |
| Pavel Zhukov | 2017-08-16 13:36:44 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | dhcp-4.2.5-61.el7 | |||
| errata-xmlrpc | 2017-08-16 13:38:20 UTC | Status | MODIFIED | ON_QA |
| Stepan Broz | 2017-10-31 10:06:20 UTC | CC | sbroz | |
| Lenka Špačková | 2017-11-13 13:31:14 UTC | Docs Contact | mdolezel | |
| Lenka Špačková | 2017-11-15 18:25:37 UTC | Docs Contact | mdolezel | igkioka |
| Pavel Zhukov | 2017-11-21 13:38:25 UTC | Doc Text | Cause – MD5 algorithm was considered insecure and should not be used in critical application Consequence – ddns updates were potentialy insecure Fix – Added support for additional algorithms. Result – Any of HMAC-SHA1, HMAC-SHA224, HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512 algorithms can be used for DDNS |
|
| Ioanna Gkioka | 2017-11-24 11:59:37 UTC | CC | pzhukov | |
| Doc Text | Cause – MD5 algorithm was considered insecure and should not be used in critical application Consequence – ddns updates were potentialy insecure Fix – Added support for additional algorithms. Result – Any of HMAC-SHA1, HMAC-SHA224, HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512 algorithms can be used for DDNS | Additional algorithms have been added for `DDNS` Previously, the `dhcpd` daemon supported only the `MD5` hashing algorithm which was considered insecure for critical applications. As a consequence, the `Dynamic DNS (DDNS)` updates were potentially insecure. This update adds support for additional algorithms, such as `HMAC-SHA1`, `HMAC-SHA224`, `HMAC-SHA256`, `HMAC-SHA384`, or `HMAC-SHA512`. | ||
| Flags | needinfo?(pzhukov) | |||
| Pavel Zhukov | 2017-11-24 15:08:27 UTC | Flags | needinfo?(pzhukov) | |
| Marek Hruscak | 2017-12-11 12:58:37 UTC | CC | mhruscak | |
| Marek Hruscak | 2017-12-11 13:32:52 UTC | Status | ON_QA | VERIFIED |
| Ioanna Gkioka | 2017-12-13 09:09:57 UTC | Doc Text | Additional algorithms have been added for `DDNS` Previously, the `dhcpd` daemon supported only the `MD5` hashing algorithm which was considered insecure for critical applications. As a consequence, the `Dynamic DNS (DDNS)` updates were potentially insecure. This update adds support for additional algorithms, such as `HMAC-SHA1`, `HMAC-SHA224`, `HMAC-SHA256`, `HMAC-SHA384`, or `HMAC-SHA512`. | `DDNS` now supports additional algorithms Previously, the `dhcpd` daemon supported only the `MD5` hashing algorithm which is considered insecure for critical applications. As a consequence, the `Dynamic DNS (DDNS)` updates were potentially insecure. This update adds support for additional algorithms: `HMAC-SHA1`, `HMAC-SHA224`, `HMAC-SHA256`, `HMAC-SHA384`, or `HMAC-SHA512`. |
| Pasi Karkkainen | 2018-01-24 20:28:55 UTC | CC | pasik | |
| Ioanna Gkioka | 2018-01-25 08:09:46 UTC | Doc Text | `DDNS` now supports additional algorithms Previously, the `dhcpd` daemon supported only the `MD5` hashing algorithm which is considered insecure for critical applications. As a consequence, the `Dynamic DNS (DDNS)` updates were potentially insecure. This update adds support for additional algorithms: `HMAC-SHA1`, `HMAC-SHA224`, `HMAC-SHA256`, `HMAC-SHA384`, or `HMAC-SHA512`. | `DDNS` now supports additional algorithms Previously, the `dhcpd` daemon supported only the `HMAC-MD5` hashing algorithm which is considered insecure for critical applications. As a consequence, the `Dynamic DNS (DDNS)` updates were potentially insecure. This update adds support for additional algorithms: `HMAC-SHA1`, `HMAC-SHA224`, `HMAC-SHA256`, `HMAC-SHA384`, or `HMAC-SHA512`. |
| PnT Account Manager | 2018-03-23 21:41:51 UTC | CC | mhruscak | |
| errata-xmlrpc | 2018-04-10 00:01:06 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2018-04-10 08:00:52 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2018-04-10 04:00:52 UTC | |||
| errata-xmlrpc | 2018-04-10 08:01:58 UTC | Link ID | Red Hat Product Errata RHBA-2018:0658 |
Back to bug 1396985