UAT for RSA key list for DTLS and SSL: need feedback and further testing.

[ivan jr sy <ivan_jr () yahoo com>]

Hi all,

To those who are interested on SSL decryption for wireshark, I would like to solicit opinions, comments and reviews for 
bug#3343 patch. Further testing is also necessary.

The patch mostly adjust the RSA keylist line like this:
127.0.0.1,443,http,/path/to/snakeoil2.key;10.1.1.1,8080,smtp,/other/path/key.pem

to user access table.
IP address
Port
Protocol
Key File
Password

and supports IPv6. For more information, please refer:

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3343#c8

Items require feedback

1. the key file is tried first using ws_fopen when you input UAT entries. However, if these keys is no longer there, it 
will prompt during startup for WS. Is this acceptable?

2. will the changes affect tshark?

3. patch uses "ChK12ProtocolsSection" for its UAT's help section. where do I start to create a new one?

4. debug file is under preference, i was thinking of one debug file per key list - but how does that go? will that be 
acceptable? If I have a frame capture of multiple SSL traffic, will that be broken down into pieces?

Thanks!


      
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe