2014-06-05 10:30:41 +00:00
|
|
|
libwiretap.so.0 libwiretap0 #MINVER#
|
|
|
|
|
file_eof@Base 1.9.1
|
|
|
|
|
file_error@Base 1.9.1
|
|
|
|
|
file_getc@Base 1.9.1
|
|
|
|
|
file_gets@Base 1.9.1
|
2018-05-17 15:51:50 +00:00
|
|
|
file_getsp@Base 2.9.0
|
2014-06-05 10:30:41 +00:00
|
|
|
file_iscompressed@Base 1.12.0~rc1
|
|
|
|
|
file_peekc@Base 1.12.0~rc1
|
|
|
|
|
file_read@Base 1.9.1
|
|
|
|
|
file_seek@Base 1.9.1
|
|
|
|
|
file_tell@Base 1.9.1
|
wiretap: more work on file type/subtypes.
Provide a wiretap routine to get an array of all savable file
type/subtypes, sorted with pcap and pcapng at the top, followed by the
other types, sorted either by the name or the description.
Use that routine to list options for the -F flag for various commands
Rename wtap_get_savable_file_types_subtypes() to
wtap_get_savable_file_types_subtypes_for_file(), to indicate that it
provides an array of all file type/subtypes in which a given file can be
saved. Have it sort all types, other than the default type/subtype and,
if there is one, the "other" type (both of which are put at the top), by
the name or the description.
Don't allow wtap_register_file_type_subtypes() to override any existing
registrations; have them always register a new type. In that routine,
if there are any emply slots in the table, due to an entry being
unregistered, use it rather than allocating a new slot.
Don't allow unregistration of built-in types.
Rename the "dump open table" to the "file type/subtype table", as it has
entries for all types/subtypes, even if we can't write them.
Initialize that table in a routine that pre-allocates the GArray before
filling it with built-in types/subtypes, so it doesn't keep getting
reallocated.
Get rid of wtap_num_file_types_subtypes - it's just a copy of the size
of the GArray.
Don't have wtap_file_type_subtype_description() crash if handed an
file type/subtype that isn't a valid array index - just return NULL, as
we do with wtap_file_type_subtype_name().
In wtap_name_to_file_type_subtype(), don't use WTAP_FILE_TYPE_SUBTYPE_
names for the backwards-compatibility names - map those names to the
current names, and then look them up. This reduces the number of
uses of hardwired WTAP_FILE_TYPE_SUBTYPE_ values.
Clean up the type of wtap_module_count - it has no need to be a gulong.
Have built-in wiretap file handlers register names to be used for their
file type/subtypes, rather than building the table in init.lua.
Add a new Lua C function get_wtap_filetypes() to construct the
wtap_filetypes table, based on the registered names, and use it in
init.lua.
Add a #define WSLUA_INTERNAL_FUNCTION to register functions intended
only for internal use in init.lua, so they can be made available from
Lua without being documented.
Get rid of WTAP_NUM_FILE_TYPES_SUBTYPES - most code has no need to use
it, as it can just request arrays of types, and the space of
type/subtype codes can be sparse due to registration in any case, so
code has to be careful using it.
wtap_get_num_file_types_subtypes() is no longer used, so remove it. It
returns the number of elements in the file type/subtype array, which is
not necessarily the name of known file type/subtypes, as there may have
been some deregistered types, and those types do *not* get removed from
the array, they just get cleared so that they're available for future
allocation (we don't want the indices of any registered types to changes
if another type is deregistered, as those indicates are the type/subtype
values, so we can't shrink the array).
Clean up white space and remove some comments that shouldn't have been
added.
2021-02-17 06:24:47 +00:00
|
|
|
get_backwards_compatibility_lua_table@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
init_open_routines@Base 1.12.0~rc1
|
2015-08-16 16:37:11 +00:00
|
|
|
merge_files@Base 1.99.9
|
2016-12-04 01:57:34 +00:00
|
|
|
merge_files_to_stdout@Base 2.3.0
|
|
|
|
|
merge_files_to_tempfile@Base 2.3.0
|
2015-08-16 16:37:11 +00:00
|
|
|
merge_idb_merge_mode_to_string@Base 1.99.9
|
|
|
|
|
merge_string_to_idb_merge_mode@Base 1.99.9
|
2014-06-05 10:30:41 +00:00
|
|
|
open_info_name_to_type@Base 1.12.0~rc1
|
|
|
|
|
open_routines@Base 1.12.0~rc1
|
2021-08-27 06:47:36 +00:00
|
|
|
pcapng_process_options@Base 3.5.0
|
|
|
|
|
pcapng_process_bytes_option@Base 3.5.0
|
|
|
|
|
pcapng_process_string_option@Base 3.5.0
|
|
|
|
|
pcapng_process_timestamp_option@Base 3.5.0
|
|
|
|
|
pcapng_process_uint8_option@Base 3.5.0
|
|
|
|
|
pcapng_process_uint32_option@Base 3.5.0
|
|
|
|
|
pcapng_process_uint64_option@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
register_pcapng_block_type_handler@Base 1.99.0
|
2014-12-17 10:06:19 +00:00
|
|
|
register_pcapng_option_handler@Base 1.99.2
|
2020-07-29 05:34:24 +00:00
|
|
|
wtap_add_generated_idb@Base 3.3.0
|
2017-12-31 15:06:16 +00:00
|
|
|
wtap_addrinfo_list_empty@Base 2.5.0
|
2021-06-21 14:56:58 +00:00
|
|
|
wtap_block_add_custom_option@Base 3.5.0
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_add_bytes_option@Base 3.5.0
|
|
|
|
|
wtap_block_add_bytes_option_borrow@Base 3.5.0
|
2021-02-01 23:56:47 +00:00
|
|
|
wtap_block_add_if_filter_option@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_add_ipv4_option@Base 2.1.2
|
|
|
|
|
wtap_block_add_ipv6_option@Base 2.1.2
|
2021-08-04 17:57:52 +00:00
|
|
|
wtap_block_add_nflx_custom_option@Base 3.5.0
|
2021-08-30 21:36:44 +00:00
|
|
|
wtap_block_add_packet_verdict_option@Base 3.5.1
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_add_string_option@Base 2.1.2
|
|
|
|
|
wtap_block_add_string_option_format@Base 2.1.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_add_uint32_option@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_add_uint64_option@Base 2.1.2
|
|
|
|
|
wtap_block_add_uint8_option@Base 2.1.2
|
|
|
|
|
wtap_block_array_free@Base 2.1.2
|
|
|
|
|
wtap_block_copy@Base 2.1.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_count_option@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_create@Base 2.1.2
|
|
|
|
|
wtap_block_foreach_option@Base 2.1.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_get_bytes_option_value@Base 3.5.0
|
2021-02-01 23:56:47 +00:00
|
|
|
wtap_block_get_if_filter_option_value@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_get_ipv4_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_get_ipv6_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_get_mandatory_data@Base 2.1.2
|
2021-08-04 17:57:52 +00:00
|
|
|
wtap_block_get_nflx_custom_option@Base 3.5.0
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_get_nth_bytes_option_value@Base 3.5.0
|
2021-08-30 21:36:44 +00:00
|
|
|
wtap_block_get_nth_packet_verdict_option_value@Base 3.5.1
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_get_nth_string_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_get_string_option_value@Base 2.1.2
|
2021-02-10 02:46:29 +00:00
|
|
|
wtap_block_get_type@Base 3.5.0
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_get_uint32_option_value@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_get_uint64_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_get_uint8_option_value@Base 2.1.2
|
2020-10-22 02:10:49 +00:00
|
|
|
wtap_block_make_copy@Base 3.3.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_ref@Base 3.5.0
|
2016-08-22 12:11:32 +00:00
|
|
|
wtap_block_remove_nth_option_instance@Base 2.2.0
|
|
|
|
|
wtap_block_remove_option@Base 2.2.0
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_set_bytes_option_value@Base 3.5.0
|
2021-02-01 23:56:47 +00:00
|
|
|
wtap_block_set_if_filter_option_value@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_set_ipv4_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_set_ipv6_option_value@Base 2.1.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_set_nth_bytes_option_value@Base 3.5.0
|
2021-08-30 21:36:44 +00:00
|
|
|
wtap_block_set_nth_packet_verdict_option_value@Base 3.5.1
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_set_nth_string_option_value@Base 2.1.2
|
2021-01-30 09:49:45 +00:00
|
|
|
wtap_block_set_nth_string_option_value_format@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_set_string_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_set_string_option_value_format@Base 2.1.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_set_uint32_option_value@Base 3.5.0
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_block_set_uint64_option_value@Base 2.1.2
|
|
|
|
|
wtap_block_set_uint8_option_value@Base 2.1.2
|
2021-04-29 11:23:21 +00:00
|
|
|
wtap_block_unref@Base 3.5.0
|
2019-01-10 01:46:55 +00:00
|
|
|
wtap_cleanup@Base 2.3.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_cleareof@Base 1.9.1
|
|
|
|
|
wtap_close@Base 1.9.1
|
2018-12-05 01:48:50 +00:00
|
|
|
wtap_compression_type_description@Base 2.9.0
|
|
|
|
|
wtap_compression_type_extension@Base 2.9.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_default_file_extension@Base 1.9.1
|
|
|
|
|
wtap_deregister_file_type_subtype@Base 1.12.0~rc1
|
|
|
|
|
wtap_deregister_open_info@Base 1.12.0~rc1
|
|
|
|
|
wtap_dump@Base 1.9.1
|
editcap, tshark: process IDBs in the middle of input files.
Instead of grabbing the set of IDBs found at open time, have a loop
using wtap_get_next_interface_description() to read all unread IDBs run
after opening the input file, after reading a packet from the input
file, and after getting an EOF on the input file.
Add a routine wtap_uses_interface_ids() to check whether the file type
and subtype for a dump file uses interface IDs and requires IDBs. If
so, in the aforementioned loop, add the IDBs to the dump stream.
Add a routine wtap_dump_add_idb() to add IDBs to a dump stream. Have it
call a file-format-specific routine to add the IDBs; the only file type
that supports it is pcapng, and it 1) writes out the IDB and 2) adds it
to the set of IDBs for the stream.
Add a wtap_dump_params_init_no_idbs() routine that prevents the IDBs
from the input file from being used to initialize the output file; use
it in cases where we're using the aforementioned loop to copy over IDBs.
Don't require any IDBs to be present when opening a pcapng file for
writing; 1) the simplest pcapng file has just an SHB in it, 2) that
requirement causes dumps that don't provide IDBs at open time to fail,
and 3) the real issue is that we don't want packets with an interface ID
not corresponding to a known IDB, and we already have a check for that.
(There are some hacks here; eventually, when everything processes the
IDBs in such a loop, we may be able to get rid of the "two favors of
dump parameter initialization" hack.)
Fixes #15844.
Addresses the same issue in #15502, but there are other issues there
that also need to be addressed.
In addition, the merge code also needs to be changed to handle this.
2020-10-22 08:10:57 +00:00
|
|
|
wtap_dump_add_idb@Base 3.3.2
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_dump_can_compress@Base 1.9.1
|
|
|
|
|
wtap_dump_can_open@Base 1.9.1
|
|
|
|
|
wtap_dump_can_write@Base 1.9.1
|
2021-03-14 21:22:16 +00:00
|
|
|
wtap_dump_can_write_encap@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_dump_close@Base 1.9.1
|
2019-02-19 18:04:02 +00:00
|
|
|
wtap_dump_discard_decryption_secrets@Base 3.0.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_dump_fdopen@Base 1.9.1
|
|
|
|
|
wtap_dump_file_encap_type@Base 1.9.1
|
|
|
|
|
wtap_dump_file_seek@Base 1.12.0~rc1
|
|
|
|
|
wtap_dump_file_tell@Base 1.12.0~rc1
|
editcap, tshark: process IDBs in the middle of input files.
Instead of grabbing the set of IDBs found at open time, have a loop
using wtap_get_next_interface_description() to read all unread IDBs run
after opening the input file, after reading a packet from the input
file, and after getting an EOF on the input file.
Add a routine wtap_uses_interface_ids() to check whether the file type
and subtype for a dump file uses interface IDs and requires IDBs. If
so, in the aforementioned loop, add the IDBs to the dump stream.
Add a routine wtap_dump_add_idb() to add IDBs to a dump stream. Have it
call a file-format-specific routine to add the IDBs; the only file type
that supports it is pcapng, and it 1) writes out the IDB and 2) adds it
to the set of IDBs for the stream.
Add a wtap_dump_params_init_no_idbs() routine that prevents the IDBs
from the input file from being used to initialize the output file; use
it in cases where we're using the aforementioned loop to copy over IDBs.
Don't require any IDBs to be present when opening a pcapng file for
writing; 1) the simplest pcapng file has just an SHB in it, 2) that
requirement causes dumps that don't provide IDBs at open time to fail,
and 3) the real issue is that we don't want packets with an interface ID
not corresponding to a known IDB, and we already have a check for that.
(There are some hacks here; eventually, when everything processes the
IDBs in such a loop, we may be able to get rid of the "two favors of
dump parameter initialization" hack.)
Fixes #15844.
Addresses the same issue in #15502, but there are other issues there
that also need to be addressed.
In addition, the merge code also needs to be changed to handle this.
2020-10-22 08:10:57 +00:00
|
|
|
wtap_dump_file_type_subtype@Base 3.3.2
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_dump_file_write@Base 1.12.0~rc1
|
|
|
|
|
wtap_dump_flush@Base 1.9.1
|
2017-08-08 07:11:33 +00:00
|
|
|
wtap_dump_get_needs_reload@Base 2.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_dump_open@Base 1.9.1
|
2015-11-10 21:52:38 +00:00
|
|
|
wtap_dump_open_stdout@Base 2.0.0
|
2016-01-25 02:18:05 +00:00
|
|
|
wtap_dump_open_tempfile@Base 2.0.0
|
2018-11-11 14:49:12 +00:00
|
|
|
wtap_dump_params_cleanup@Base 2.9.0
|
2019-02-19 18:04:02 +00:00
|
|
|
wtap_dump_params_discard_decryption_secrets@Base 3.0.0
|
2018-11-11 14:49:12 +00:00
|
|
|
wtap_dump_params_init@Base 2.9.0
|
editcap, tshark: process IDBs in the middle of input files.
Instead of grabbing the set of IDBs found at open time, have a loop
using wtap_get_next_interface_description() to read all unread IDBs run
after opening the input file, after reading a packet from the input
file, and after getting an EOF on the input file.
Add a routine wtap_uses_interface_ids() to check whether the file type
and subtype for a dump file uses interface IDs and requires IDBs. If
so, in the aforementioned loop, add the IDBs to the dump stream.
Add a routine wtap_dump_add_idb() to add IDBs to a dump stream. Have it
call a file-format-specific routine to add the IDBs; the only file type
that supports it is pcapng, and it 1) writes out the IDB and 2) adds it
to the set of IDBs for the stream.
Add a wtap_dump_params_init_no_idbs() routine that prevents the IDBs
from the input file from being used to initialize the output file; use
it in cases where we're using the aforementioned loop to copy over IDBs.
Don't require any IDBs to be present when opening a pcapng file for
writing; 1) the simplest pcapng file has just an SHB in it, 2) that
requirement causes dumps that don't provide IDBs at open time to fail,
and 3) the real issue is that we don't want packets with an interface ID
not corresponding to a known IDB, and we already have a check for that.
(There are some hacks here; eventually, when everything processes the
IDBs in such a loop, we may be able to get rid of the "two favors of
dump parameter initialization" hack.)
Fixes #15844.
Addresses the same issue in #15502, but there are other issues there
that also need to be addressed.
In addition, the merge code also needs to be changed to handle this.
2020-10-22 08:10:57 +00:00
|
|
|
wtap_dump_params_init_no_idbs@Base 3.3.2
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_dump_set_addrinfo_list@Base 1.9.1
|
2019-01-10 01:46:55 +00:00
|
|
|
wtap_encap_description@Base 2.9.1
|
|
|
|
|
wtap_encap_name@Base 2.9.1
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_encap_requires_phdr@Base 1.9.1
|
|
|
|
|
wtap_fdclose@Base 1.9.1
|
|
|
|
|
wtap_fdreopen@Base 1.9.1
|
|
|
|
|
wtap_file_encap@Base 1.9.1
|
|
|
|
|
wtap_file_get_idb_info@Base 1.9.1
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_file_get_nrb@Base 2.1.2
|
2020-05-01 17:28:04 +00:00
|
|
|
wtap_file_get_num_shbs@Base 3.3.0
|
2015-07-20 15:09:06 +00:00
|
|
|
wtap_file_get_shb@Base 1.99.9
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_file_size@Base 1.9.1
|
2014-09-29 02:07:15 +00:00
|
|
|
wtap_file_tsprec@Base 1.99.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_file_type_subtype@Base 1.12.0~rc1
|
2021-02-13 08:03:51 +00:00
|
|
|
wtap_file_type_subtype_description@Base 3.5.0
|
|
|
|
|
wtap_file_type_subtype_name@Base 3.5.0
|
wiretap: have file handlers advertise blocks and options supported.
Instead of a "supports name resolution" Boolean and bitflags for types of
comments supported, provide a list of block types that the file
type/subtype supports, with each block type having a list of options
supported. Indicate whether "supported" means "one instance" or
"multiple instances".
"Supports" doesn't just mean "can be written", it also means "could be
read".
Rename WTAP_BLOCK_IF_DESCRIPTION to WTAP_BLOCK_IF_ID_AND_INFO, to
indicate that it provides, in addition to information about the
interface, an ID (implicitly, in pcapng files, by its ordinal number)
that is associated with every packet in the file. Emphasize that in
comments - just because your capture file format can list the interfaces
on which a capture was done, that doesn't mean it supports this; it
doesn't do so if the file doesn't indicate, for every packet, on which
of those interfaces it was captured (I'm looking at *you*, Microsoft
Network Monitor...).
Use APIs to query that information to do what the "does this file
type/subtype support name resolution information", "does this file
type/subtype support all of these comment types", and "does this file
type/subtype support - and require - interface IDs" APIs did.
Provide backwards compatibility for Lua.
This allows us to eliminate the WTAP_FILE_TYPE_SUBTYPE_ values for IBM's
iptrace; do so.
2021-02-21 22:18:04 +00:00
|
|
|
wtap_file_type_subtype_supports_block@Base 3.5.0
|
|
|
|
|
wtap_file_type_subtype_supports_option@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_free_extensions_list@Base 1.9.1
|
2015-08-20 18:38:35 +00:00
|
|
|
wtap_free_idb_info@Base 1.99.9
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_fstat@Base 1.9.1
|
2016-09-10 17:29:49 +00:00
|
|
|
wtap_get_all_capture_file_extensions_list@Base 2.3.0
|
2018-12-05 01:48:50 +00:00
|
|
|
wtap_get_all_compression_type_extensions_list@Base 2.9.0
|
2018-07-06 09:06:56 +00:00
|
|
|
wtap_get_all_file_extensions_list@Base 2.6.2
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_get_bytes_dumped@Base 1.9.1
|
2018-11-16 04:06:36 +00:00
|
|
|
wtap_get_compression_type@Base 2.9.0
|
2015-08-16 16:37:11 +00:00
|
|
|
wtap_get_debug_if_descr@Base 1.99.9
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_get_file_extension_type_extensions@Base 1.12.0~rc1
|
|
|
|
|
wtap_get_file_extension_type_name@Base 1.12.0~rc1
|
|
|
|
|
wtap_get_file_extensions_list@Base 1.9.1
|
Add a routine to get the next as-yet-unfetched interface description.
In a wtap, keep track of the first interface description not yet fetched
with wtap_get_next_interface_description() and, when
wtap_get_next_interface_description() is called, have it return that
description, as a wtap_block_t for its IDB. If there are no
as-yet-unfetched interface descriptions, return NULL; there may, in the
future, be more interface descriptions for the file, so this should be
called:
* after the file is opened;
* after wtap_read() returns TRUE, indicating that it's returned a
record (and *before* you process the record that wtap_read()
returns, as it might be the interface description for the
interface on which the packet in that record arrived);
* after wtap_read() returns FALSE, indicating an EOF or an error
return (as there might have been interfaces at the end of the
file or before the error point).
At each of those points, the caller should loop until
wtap_get_next_interface_description() returns NULL.
Not used yet (but tested with capinfos, which found a reason why you
have to wait until the end of the file before processing the interface
information - there's now a comment in the code giving that reason).
This will probably be used in the future.
2020-10-21 09:51:25 +00:00
|
|
|
wtap_get_next_interface_description@Base 3.3.2
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_get_num_encap_types@Base 1.9.1
|
|
|
|
|
wtap_get_num_file_type_extensions@Base 1.12.0~rc1
|
wiretap: more work on file type/subtypes.
Provide a wiretap routine to get an array of all savable file
type/subtypes, sorted with pcap and pcapng at the top, followed by the
other types, sorted either by the name or the description.
Use that routine to list options for the -F flag for various commands
Rename wtap_get_savable_file_types_subtypes() to
wtap_get_savable_file_types_subtypes_for_file(), to indicate that it
provides an array of all file type/subtypes in which a given file can be
saved. Have it sort all types, other than the default type/subtype and,
if there is one, the "other" type (both of which are put at the top), by
the name or the description.
Don't allow wtap_register_file_type_subtypes() to override any existing
registrations; have them always register a new type. In that routine,
if there are any emply slots in the table, due to an entry being
unregistered, use it rather than allocating a new slot.
Don't allow unregistration of built-in types.
Rename the "dump open table" to the "file type/subtype table", as it has
entries for all types/subtypes, even if we can't write them.
Initialize that table in a routine that pre-allocates the GArray before
filling it with built-in types/subtypes, so it doesn't keep getting
reallocated.
Get rid of wtap_num_file_types_subtypes - it's just a copy of the size
of the GArray.
Don't have wtap_file_type_subtype_description() crash if handed an
file type/subtype that isn't a valid array index - just return NULL, as
we do with wtap_file_type_subtype_name().
In wtap_name_to_file_type_subtype(), don't use WTAP_FILE_TYPE_SUBTYPE_
names for the backwards-compatibility names - map those names to the
current names, and then look them up. This reduces the number of
uses of hardwired WTAP_FILE_TYPE_SUBTYPE_ values.
Clean up the type of wtap_module_count - it has no need to be a gulong.
Have built-in wiretap file handlers register names to be used for their
file type/subtypes, rather than building the table in init.lua.
Add a new Lua C function get_wtap_filetypes() to construct the
wtap_filetypes table, based on the registered names, and use it in
init.lua.
Add a #define WSLUA_INTERNAL_FUNCTION to register functions intended
only for internal use in init.lua, so they can be made available from
Lua without being documented.
Get rid of WTAP_NUM_FILE_TYPES_SUBTYPES - most code has no need to use
it, as it can just request arrays of types, and the space of
type/subtype codes can be sparse due to registration in any case, so
code has to be careful using it.
wtap_get_num_file_types_subtypes() is no longer used, so remove it. It
returns the number of elements in the file type/subtype array, which is
not necessarily the name of known file type/subtypes, as there may have
been some deregistered types, and those types do *not* get removed from
the array, they just get cleared so that they're available for future
allocation (we don't want the indices of any registered types to changes
if another type is deregistered, as those indicates are the type/subtype
values, so we can't shrink the array).
Clean up white space and remove some comments that shouldn't have been
added.
2021-02-17 06:24:47 +00:00
|
|
|
wtap_get_savable_file_types_subtypes_for_file@Base 3.5.0
|
|
|
|
|
wtap_get_writable_file_types_subtypes@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_has_open_info@Base 1.12.0~rc1
|
2016-12-04 22:25:10 +00:00
|
|
|
wtap_init@Base 2.3.0
|
2019-01-10 01:46:55 +00:00
|
|
|
wtap_name_to_encap@Base 2.9.1
|
2021-02-13 08:03:51 +00:00
|
|
|
wtap_name_to_file_type_subtype@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_open_offline@Base 1.9.1
|
2016-07-15 03:29:41 +00:00
|
|
|
wtap_opttypes_initialize@Base 2.1.2
|
2017-02-04 15:26:34 +00:00
|
|
|
wtap_opttypes_cleanup@Base 2.3.0
|
2021-08-30 21:36:44 +00:00
|
|
|
wtap_packet_verdict_free@Base 3.5.1
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_pcap_encap_to_wtap_encap@Base 1.9.1
|
2021-02-23 09:18:31 +00:00
|
|
|
wtap_pcap_file_type_subtype@Base 3.5.0
|
|
|
|
|
wtap_pcap_nsec_file_type_subtype@Base 3.5.0
|
|
|
|
|
wtap_pcapng_file_type_subtype@Base 3.5.0
|
2021-02-06 16:35:51 +00:00
|
|
|
wtap_plugins_supported@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_read@Base 1.9.1
|
2014-11-24 15:30:52 +00:00
|
|
|
wtap_read_bytes@Base 1.99.1
|
|
|
|
|
wtap_read_bytes_or_eof@Base 1.99.1
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_read_packet_bytes@Base 1.12.0~rc1
|
|
|
|
|
wtap_read_so_far@Base 1.9.1
|
2018-02-09 11:04:29 +00:00
|
|
|
wtap_rec_cleanup@Base 2.5.1
|
|
|
|
|
wtap_rec_init@Base 2.5.1
|
2021-08-04 17:18:46 +00:00
|
|
|
wtap_rec_reset@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_register_encap_type@Base 1.9.1
|
|
|
|
|
wtap_register_file_type_extension@Base 1.12.0~rc1
|
2021-02-24 03:10:35 +00:00
|
|
|
wtap_register_file_type_subtype@Base 3.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_register_open_info@Base 1.12.0~rc1
|
2017-09-30 23:56:03 +00:00
|
|
|
wtap_register_plugin@Base 2.5.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_seek_read@Base 1.9.1
|
|
|
|
|
wtap_sequential_close@Base 1.9.1
|
|
|
|
|
wtap_set_bytes_dumped@Base 1.9.1
|
2018-11-18 17:11:42 +00:00
|
|
|
wtap_set_cb_new_secrets@Base 2.9.0
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_set_cb_new_ipv4@Base 1.9.1
|
|
|
|
|
wtap_set_cb_new_ipv6@Base 1.9.1
|
|
|
|
|
wtap_snapshot_length@Base 1.9.1
|
|
|
|
|
wtap_strerror@Base 1.9.1
|
2015-08-16 16:37:11 +00:00
|
|
|
wtap_tsprec_string@Base 1.99.9
|
2021-09-27 11:10:43 +00:00
|
|
|
wtap_uses_lua_filehandler@Base 3.5.1
|
2014-06-05 10:30:41 +00:00
|
|
|
wtap_write_shb_comment@Base 1.9.1
|