WS4.4 hang during initialization after RSA key entry
Trying to decode a TLS stream in WS 4.4, I loaded an RSA key file as per instructions but WS hung at that point, so I force-quitted and it hasn't started since. It hangs at the point of "Initialising tap listeners" or sometimes "Loading module preferences" with 100% CPU usage according to Activity Monitor.
I've tried removing the application and its configuration as per instructions, restarting the machine from cold and then reinstalling from scratch, but no help. I've browsed around SO and found this but it relates to an older version of WS and the config files it says to delete aren't anywhere to be found, at least by me. Having said that, it is the exact same problem, I think - trying to load RSA keys, then crashing, then hanging on restart. Some other posts refer to this issue but on Windows, and the fixes don't carry across.
Running WS 4.4 application bundle downloaded from here on MacOS Sequoia/Intel
How large is the key file? Are you opening Wireshark and immediately trying to dissect TLS, perhaps by double clicking a capture file to open Wireshark, or does this happen if you start Wireshark without opening a file or starting a capture?
https://gitlab.com/wireshark/wireshar...https://gitlab.com/wireshark/wireshar...
I put a long answer to this comment earlier, but it seems to have gotten lost. Anyway, things have moved on a little bit. To answer your question though, the key file is the RSA key file, not the SSLKEYLOGFILE, so it's just the size of an RSA private key. And it hangs when launching the app - not opening a capture file and before you get to do a capture of any sort.
When I said earlier that things have moved on, I tried installing under a different user, and it seems to work ok. Suggests these a bit of per-user config that's left behind in the de-installation process, that broke in the original crash, that's preventing the app from starting. Any thoughts what that might be?
You can look at your preference files to see what is different, but I can imagine a similar situation to the SSLKEYLOG issue where if the RSA Key file is the same as the TLS debug log there could be an infinite loop
Hallelujah - the culprit is the "ssl_keys" file in the config directory. I deleted it, and now WS starts. I was looking in the wrong place for the config directory. Thanks for your help.