http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2170
------- Comment #4 from jyoung@xxxxxxx 2008-01-08 09:56 GMT -------
Yes this a bug.
Actually there are multiple problems here. These problems will (eventually)
be addressed as the various (volunteer) programmers get the time/ability/desire
to work on them.
In this case the sscp_users file built by Wireshark's using the SSCP Users
Table dialog can NOT be successfuly read in by Wireshark. The problem appears
to be caused if any the four fields of a sscp_users file record are an empty
string (e.g. "").
Your instructions to reproduce this problem deliberatly left the "ni" and
"called_pc" fields empty. One possible workaround is to NOT leave any of these
fields empty.
The fixes for this problem should include augmenting the SSCP Users Table
dialog so that it produces valid sscp_users config files.
Also the module he reads in the sscp_users config file should be augmented to
more gracefully handle malformed records.
And if empty fields are indeed valid in SSCP Users Tables records then the
module that reads in the recordds will need to handle this case as well.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.