Wireshark-bugs: [Wireshark-bugs] [Bug 8763] Wireshark writes empty NRB FQDN which makes trace un

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 09 Jun 2013 02:40:32 +0000

Comment # 2 on bug 8763 from 
I'm not sure there's a good reason to treat a zero-length name in an NRB as a
fatal error, so in r49851 I changed it to just ignore zero-length names.  I'll
schedule that for backporting to 1.10 and 1.8.

That handles half the problem (unless you're stuck with 1.6).

The other half probably should be fixed in the name resolution code; even if
you *don't* save the file, after you resolve that IP address the packet detail
pane entry for the source address looks weird with the zero-length name.  RFC
1034 doesn't seem to like NUL as a character in a label, so if a PTR query
returns a zero byte in the answer record, that's a misconfiguration, unless
some subsequent RFC says it's OK.

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