Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+512\s+byte\s+limit\s+on\s+trap\s+variables\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[nv\-l\]\s+512\s+byte\s+limit\s+on\s+trap\s+variables\s*$/: 2 ]

Total 2 documents matching your query.

1. [nv-l] 512 byte limit on trap variables (score: 1): Author: "Qureshi, Fawad" <Fawad.Qureshi AT ssa DOT gov>; Date: Wed, 4 Aug 2004 16:10:44 -0400; Is the 512 byte limit for trap variables still enforced? If yes, would this mean any individual varbind cannot be more then 512 bytes or the total of all varbinds can not be more then 512 bytes in le; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-08/msg00020.html (11,683 bytes)
2. Re: [nv-l] 512 byte limit on trap variables (score: 1): Author: James Shanks <jshanks AT us.ibm DOT com>; Date: Thu, 5 Aug 2004 09:24:29 -0400; It's 512-bytes per varbind and it is enforced as a result of a CERT advisory which indicated that people might seek to gain control of your system by sending cunningly-designed traps which would allo; /usr/local/webapp/mharc-adsm.org/html/nv-l/2004-08/msg00023.html (12,921 bytes)

Current List: 1 - 2
Page: [1]