Back to bug 1315481

Who When What Removed Added
Bryan Totty 2016-03-07 21:10:30 UTC Priority unspecified medium
Robert Story 2016-03-07 21:45:48 UTC CC rs
Jan Safranek 2016-03-08 08:57:48 UTC Status NEW ASSIGNED
Mohit Agrawal 2016-03-18 04:30:23 UTC CC moagrawa
Mohit Agrawal 2016-04-06 05:34:15 UTC Blocks 1324306
Zdenek Pytela 2016-07-01 09:49:46 UTC CC jsafrane, zpytela
Flags needinfo?(jsafrane)
Jan Safranek 2016-07-04 08:02:34 UTC Flags needinfo?(jsafrane)
Tomas Mlcoch 2016-07-12 12:28:40 UTC Assignee jsafrane jridky
Chris Williams 2016-07-14 15:17:46 UTC Blocks 1269194
Josef Ridky 2016-07-21 08:37:53 UTC Blocks 1356044
Tomáš Hozza 2016-07-25 13:17:31 UTC Keywords FastFix
Filip Krska 2016-07-31 09:31:50 UTC Keywords EasyFix, Patch, Reproducer
Priority medium urgent
CC fkrska
Severity medium high
Honza Horak 2016-07-31 16:02:17 UTC CC hhorak
Marcel Kolaja 2016-08-01 10:59:07 UTC CC mkolaja
Josef Ridky 2016-08-01 13:19:47 UTC Status ASSIGNED MODIFIED
Fixed In Version net-snmp-5.5-58.el6
Marcel Kolaja 2016-08-03 07:22:53 UTC Blocks 1363606
Marcel Kolaja 2016-08-03 07:23:22 UTC Keywords ZStream
Dalibor Pospíšil 2016-08-10 11:15:18 UTC CC dapospis
QA Contact qe-baseos-security dapospis
Mirek Jahoda 2016-08-22 14:59:54 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 by the _sess_async_send() function and the SNMP response is no longer timed out or too long.
Mirek Jahoda 2016-08-22 15:04:28 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 by the _sess_async_send() function and the SNMP response is no longer timed out or too long. 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:29 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.
errata-xmlrpc 2016-09-09 08:26:13 UTC Status MODIFIED ON_QA
Filip Krska 2016-09-09 13:58:05 UTC CC jridky
Flags needinfo?(jridky)
Josef Ridky 2016-09-13 14:38:53 UTC Flags needinfo?(jridky)
Dalibor Pospíšil 2016-12-12 15:24:46 UTC Status ON_QA VERIFIED
errata-xmlrpc 2017-03-21 00:30:11 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2017-03-21 09:24:43 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2017-03-21 05:24:43 UTC

Back to bug 1315481