Back to bug 1324306
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jan Safranek | 2016-04-07 08:33:50 UTC | Status | NEW | ASSIGNED |
| Version | 7.4 | 7.2 | ||
| Tomas Mlcoch | 2016-07-12 12:17:11 UTC | CC | rstory | |
| Assignee | jsafrane | jridky | ||
| Dalibor Pospíšil | 2016-08-10 11:15:51 UTC | CC | dapospis | |
| QA Contact | qe-baseos-security | dapospis | ||
| Mirek Jahoda | 2016-08-22 15:04:18 UTC | CC | mjahoda | |
| Docs Contact | mjahoda | |||
| Doc Text | Previously, all the following SNMPv1 and SNMPv2c responses were checked against the last recorded SNMPv3 max message size property. As a consequence, an SNMPv3 request with a small max message size could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked for SNMPv3 requests only, and the SNMPv1 and SNMPv2c response is no longer timed out or too long. | |||
| Mirek Jahoda | 2016-08-22 15:25:40 UTC | Doc Text | Previously, all the following SNMPv1 and SNMPv2c responses were checked against the last recorded SNMPv3 max message size property. As a consequence, an SNMPv3 request with a small max message size could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked for SNMPv3 requests only, and the SNMPv1 and SNMPv2c response is no longer timed out or too long. | Previously, all the SNMPv1 and SNMPv2c responses that followed an SNMPv3 message were checked against the last recorded SNMPv3 "max message size" property. As a consequence, an SNMPv3 request with a small "max message size" could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked only for SNMPv3 requests, and the SNMPv1 and SNMPv2c response is no longer timed out. |
| Josef Ridky | 2016-10-25 12:58:45 UTC | Blocks | 1380364 | |
| Ondrej Vasik | 2016-12-09 12:00:29 UTC | Blocks | 1393870 | |
| Ondrej Vasik | 2017-01-10 14:37:27 UTC | CC | ovasik | |
| Josef Ridky | 2017-01-16 11:32:53 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | net-snmp-5.7.2-25.el7 | |||
| errata-xmlrpc | 2017-01-16 11:35:50 UTC | Status | MODIFIED | ON_QA |
| Marie Hornickova | 2017-03-15 10:44:26 UTC | Doc Type | Bug Fix | Release Note |
| Jan Blazek | 2017-03-23 09:59:53 UTC | Status | ON_QA | VERIFIED |
| Mirek Jahoda | 2017-04-19 13:25:33 UTC | Doc Text | Previously, all the SNMPv1 and SNMPv2c responses that followed an SNMPv3 message were checked against the last recorded SNMPv3 "max message size" property. As a consequence, an SNMPv3 request with a small "max message size" could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked only for SNMPv3 requests, and the SNMPv1 and SNMPv2c response is no longer timed out. | SNMP response is no longer timed out Previously, all the SNMPv1 and SNMPv2c responses that followed an SNMPv3 message were checked against the last recorded SNMPv3 "max message size" property. As a consequence, an SNMPv3 request with a small "max message size" could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked only for SNMPv3 requests, and the SNMPv1 and SNMPv2c response is no longer timed out. |
| Doc Type | Release Note | Bug Fix | ||
| Mirek Jahoda | 2017-05-18 19:04:26 UTC | Doc Text | SNMP response is no longer timed out Previously, all the SNMPv1 and SNMPv2c responses that followed an SNMPv3 message were checked against the last recorded SNMPv3 "max message size" property. As a consequence, an SNMPv3 request with a small "max message size" could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked only for SNMPv3 requests, and the SNMPv1 and SNMPv2c response is no longer timed out. | SNMP response is no longer timed out Previously, all the Simple Network Management Protocol version 1 (SNMPv1) and SNMPv2c responses that followed an SNMPv3 message were checked against the last recorded SNMPv3 "max message size" property. As a consequence, an SNMPv3 request with a small "max message size" could lead to SNMPv1 and SNMPv2c bulk requests timing out. With this update, the session maximum message size is checked only for SNMPv3 requests, and the SNMPv1 and SNMPv2c response is no longer timed out. |
| errata-xmlrpc | 2017-08-01 15:58:57 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2017-08-01 11:58:57 UTC |
Back to bug 1324306