diff options
| author | Guy Harris <guy@alum.mit.edu> | 2019-05-27 18:11:45 -0700 |
|---|---|---|
| committer | Guy Harris <guy@alum.mit.edu> | 2019-05-28 01:16:50 +0000 |
| commit | 3a56285ffb438d015e99c753f8c4198606fb0a19 (patch) | |
| tree | 55791b0064fe921720487f64b062cf3797a0eac8 | |
| parent | 0ac699d621ab1e033cd7b3d576b2e746932e82b8 (diff) | |
Note, in a comment, some weird characters that appear in wildcards.
At least some NCP operations that do file enumeration take wildcard
strings, with special codes for "special" variants of the asterisk and
question mark wildcards and the component separator period.
We should figure out how to display those "special" characters (put an
overbar above them, or something such as that?)
Change-Id: I4e455f47ae3a701004fe7989b44b64a77b26e828
Reviewed-on: https://code.wireshark.org/review/33398
Reviewed-by: Guy Harris <guy@alum.mit.edu>
| -rw-r--r-- | epan/dissectors/packet-ncp.c | 32 |
1 files changed, 31 insertions, 1 deletions
diff --git a/epan/dissectors/packet-ncp.c b/epan/dissectors/packet-ncp.c index b62e9b31f1..56dd33928d 100644 --- a/epan/dissectors/packet-ncp.c +++ b/epan/dissectors/packet-ncp.c @@ -28,9 +28,39 @@ increase each time the file is reloaded). */ +/* + * On page 86 of + * + * https://www.novell.com/documentation/developer/smscomp/pdfdoc/sms_docs/sms_docs.pdf + * + * it says: + * + * The following table lists the wild cards options that can be used in + * the terminal path node. + * + * Value Option Description + * 0x2A ASTERISK Regular asterisk + * 0x3F QUESTION Regular question mark + * 0xAE SPERIOD Special Period-the most significant bit set + * 0xAA SASTERISK. Special Asterisk-the most significant bit set. + * 0xBF SQUESTION Special Question-with the most significant bit set. + * + * ASTERISK is '*', and QUESTION is '?'; the "special" versions correspond + * to the corresponding ASCII character, but with the upper bit set. + * + * They do not indicate what "special" means here. During the painful + * process at NetApp of reverse-engineering SMB server wildcard matching; + * it turned out that "traditional 8.3 name" matching and "long name" + * matching behave differently, and there were separate code points for + * "traditional 8.3 name" wildcards and period and "long name" wildcards + * and period, so that might be what's involved here. + * + * How should we display them? Show the character in question plus a + * Unicode COMBINING OVERLINE (U+0305), so they show up as {period, + * asterisk, question mark} with an overline, for example? + */ #include "config.h" - #include <epan/packet.h> #include <epan/prefs.h> #include <epan/srt_table.h> |