https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3343
--- Comment #6 from Ivan Sy <ivan_jr@xxxxxxxxx> 2009-12-02 11:25:24 PST ---
thanks for the advise, I'm currently working on this, learning UAT and dealing
with extending ssl decryption.
attached is a work-in-progress, those interested can provide feedback and more
tips! :)
done so far:
1. IPv6 support
2. UI for UAT
3. loop thru the UAT entries and add the SSL associations
4. able to have multiple IPv4 addresses and IPv6 addresses in UAT, once a
packet capture is opened, it will decrypt and outputs the debug to one file.
current issues:
1. Sometimes (1 out of 5 times), after building and running wireshark through
on a Vista with VS2008. A message will display:
"This application has requested the Runtime to terminate it ... "
2. (2 out of 5 times) when I close WS, "Wireshark has stopped working"
3. rarely, there's "Runtime Error!"
4. need debugging tools.
5. how to tie packet-dtls with these changes. or just use another function
name?
in progress:
1. uncompress ipv6 address
2. support for 'any', 'anyipv4' and 'anyipv6'
3. to write debug on multiple ssl_debug_file (one per UAT entry).
4. validate/exclude the UAT entries if the keyfile is not accessible, and if
password is not good for the p12 file. debug accordingly (if it passed
validation)
5. validate IPv4/v6 address input, port number and if the protocol dissector
exists.
wishlist:
1. migrate contents of an existing ssl_key_list file to UAT entries, and advise
that the file can be deleted. (as a pop-up message?)
2. adding SSL association is done automatically upon opening wireshark.
should'nt this be configurable instead? or triggered on the toolbar or
something?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.