https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12804
--- Comment #15 from Tomasz Mon <deso...@gmail.com> ---
(In reply to Peter Wu from comment #14)
> Tomasz' fix for Bug 16059 might actually address the root cause of this bug.
> Tomasz, should I close this bug as a duplicate of the other?
>
> The key log file is not expected to contain duplicates, so the existing use
> of wmem_file_scoped memory seemed fine. If that is somehow changed, then all
> users of the returned memory must be audited to avoid use-after-frees when
> hashtable entries are overwritten.
The key log entires are not the only ones that are subject to duplicates. The
fix to 16059 pretty much eliminates the insane amount of duplicate allocations
in TLS hash tables.
When opening my reference TLS pcapng file (simply captured youtube traffic on
my computer), I observed (total) 214 obsolete entries in "Client Random" and
"Session ID".
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
