Ethereal-dev: [Ethereal-dev] 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 Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: Richard Sharpe <rsharpe@xxxxxxxxxxxxxxxxx>
Date: Thu, 22 May 2003 14:13:21 -0700 (PDT)
Hi, 

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!

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.

Regards
-----
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, 
sharpe[at]ethereal.com, http://www.richardsharpe.com