1 | initial version |
smb.file
is an FT_STRING with BASE_NONE. Based on that Wireshark thinks the contents of those fields should not be Unicode. I don't know much about SMB but I'd think that it can be Unicode.
Changing smb.file
and smb2.filename
to use STR_UNICODE would probably fix the issue.
I'd suggest opening a bug report; please be sure to include a sample capture.
2 | No.2 Revision |
smb.file
is an FT_STRING FT_STRING
with BASE_NONE. BASE_NONE
. Based on that Wireshark thinks the contents of those fields should not be Unicode. I don't know much about SMB but I'd think that it can be Unicode.
Changing smb.file
and smb2.filename
to use STR_UNICODE would probably fix the issue.
I'd suggest opening a bug report; please be sure to include a sample capture.