Wireshark-bugs: [Wireshark-bugs] [Bug 10469] iSCSI dissector rejects PDUs with "expected data tr
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Tue, 07 Oct 2014 04:51:52 +0000

Comment # 15 on bug 10469 from 
(In reply to Bill Meier from comment #12)
> > 
> > I went through the RFC and a couple of implementations, no else seems to be
> > imposing this restriction. Might be legacy code since the commit is from
> > 2006.
> 
> Looking at the commit message (for the patch which added the test), I now
> realize that the test was added to improve the "heuristic test" to verify
> that the packet is actually an iSCSI packet.
> 
> Question: would it be correct to say that the "expected data length" field
> for a SCSI_COMMAND must always be non-zero ?

Hi, I had posted this bug. Even I do not exactly know the complete ins and outs
of the iSCSI restrictions imposed (if any), but this I am sure that for
SCSI_COMMANDs, the "expected data length" supports both zero and non-zero
values. If required by you, I could share a couple captures indicating the
same.

You are receiving this mail because:
  • You are watching all bug changes.