Re: Question on usm_parse_security_parameters

>>>>> On Wed, 21 Sep 2005 12:15:45 -0700 (PDT), rwilcox <mail-account-00001@sbcglobal.net> said:

rwilcox> This is a problem for me because after enginetime exceeds
rwilcox> 65535, I begin receiving REPORT-PDUs and then I see other
rwilcox> corruption I am currently attributing to this 4 byte vs 2
rwilcox> byte issue. I was going to just change it and submit a
rwilcox> patch, but usm_parse_security_parameters actually parses
rwilcox> msgAuthoritativeEngineTime as a long and then casts it to
rwilcox> u_int. So, I thought it appropriate to ask the three
rwilcox> wisemen(I'm sure there's more, just doesn't sound as
rwilcox> good)......

Err.... Ok, you're the *very first person* to ever report an
environment where an u_int is actually only 16bits. Unfortunately, I
suspect you'll find that this is hardly the only place that you'll run
into the issue. To be honest, you should probably typedef u_int to a
real 32 bit unsigned because there are a bunch of places in the code
where this is likely needed. You'll have to do the same for other
types as well. If you're lucky your compiler will let you typedef int
to something that is 32 bits as well....

--
Wes Hardaker
Sparta, Inc.


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/...et-snmp-coders