Ethereal-dev: [Ethereal-dev] Re: SECINFO reply in NFSv4 seems to be incorrectly dissected

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Mike Frisch <mfrisch@xxxxxxxxxx>
Date: Thu, 22 May 2003 17:21:37 -0400
On Thu, May 22, 2003 at 02:13:21PM -0700, Richard Sharpe wrote:
> According to my reading of RFC3530, 14.2.31, a SECINFO reply will contain, 
> if the status is NFSok, and array of structures containing the OIDs of the 
> mechanisms allowed.
> 
> In particular, it is not a Value Follows followed by 0 or one sec info 
> structures ... which is how it is currently dissected ...
> 
> Ahhh, I see the problem. packet-nfs.c has it coded to dissect a list 
> rather than an array!

Feel free to fix it :)  I wrote the dissector for NFSv4, but it has been
a while since I've worked on NFSv4 and as such, the dissector may not be
in sync with the current protocol specification.  I have received ZERO
feedback about the dissector, so I presume nobody is using it.  I _know_
it has bugs.  A majority of the code was written long before a complete
working NFSv4 client or server were available for testing.

> BTW, why are the signatures for dissect_rpc_list and dissect_rpc_array 
> inconsistent? I would expect both of them to take an hf_index, or neither 
> to do so.

Sorry, I cannot comment here.  I have not looked at this code in a
while.

Mike.