forked from osmocom/wireshark
ssh: make fields for string types FT_STRING rather than FT_STRINGZ.
To quote RFC 4251, "The Secure Shell (SSH) Protocol Architecture", section 5 "Data Type Representations Used in the SSH Protocols": string Arbitrary length binary string. Strings are allowed to contain arbitrary binary data, including null characters and 8-bit characters. They are stored as a uint32 containing its length (number of bytes that follow) and zero (= empty string) or more bytes that are the value of the string. Terminating null characters are not used. Strings are also used to store text. In that case, US-ASCII is used for internal names, and ISO-10646 UTF-8 for text that might be displayed to the user. The terminating null character SHOULD NOT normally be stored in the string. For example: the US-ASCII string "testing" is represented as 00 00 00 07 t e s t i n g. The UTF-8 mapping does not alter the encoding of US-ASCII characters. "Terminating null characters are not used." means "these aren't null-terminated strings; FT_STRINGZ is for null-terminated strings, but these are counted strings, for which FT_STRING si the right type. Change-Id: I217d527847a20b640bf141a5d8d56f31456af04c Reviewed-on: https://code.wireshark.org/review/38118 Petri-Dish: Guy Harris <gharris@sonic.net> Tested-by: Petri Dish Buildbot Reviewed-by: Guy Harris <gharris@sonic.net>
This commit is contained in:
parent
d5fe2d494c
commit
fed91de7a1
|
@ -1853,52 +1853,52 @@ proto_register_ssh(void)
|
|||
|
||||
{ &hf_ssh_kex_algorithms,
|
||||
{ "kex_algorithms string", "ssh.kex_algorithms",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_server_host_key_algorithms,
|
||||
{ "server_host_key_algorithms string", "ssh.server_host_key_algorithms",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_encryption_algorithms_client_to_server,
|
||||
{ "encryption_algorithms_client_to_server string", "ssh.encryption_algorithms_client_to_server",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_encryption_algorithms_server_to_client,
|
||||
{ "encryption_algorithms_server_to_client string", "ssh.encryption_algorithms_server_to_client",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_mac_algorithms_client_to_server,
|
||||
{ "mac_algorithms_client_to_server string", "ssh.mac_algorithms_client_to_server",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_mac_algorithms_server_to_client,
|
||||
{ "mac_algorithms_server_to_client string", "ssh.mac_algorithms_server_to_client",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_compression_algorithms_client_to_server,
|
||||
{ "compression_algorithms_client_to_server string", "ssh.compression_algorithms_client_to_server",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_compression_algorithms_server_to_client,
|
||||
{ "compression_algorithms_server_to_client string", "ssh.compression_algorithms_server_to_client",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_languages_client_to_server,
|
||||
{ "languages_client_to_server string", "ssh.languages_client_to_server",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_languages_server_to_client,
|
||||
{ "languages_server_to_client string", "ssh.languages_server_to_client",
|
||||
FT_STRINGZ, BASE_NONE, NULL, 0x0,
|
||||
FT_STRING, BASE_NONE, NULL, 0x0,
|
||||
NULL, HFILL }},
|
||||
|
||||
{ &hf_ssh_kex_algorithms_length,
|
||||
|
|
Loading…
Reference in New Issue