Revision history  [back]

While the answer of @johnthacker is geared towards a (long-term) solution, there might be a workaround for your workflow. If there is a pattern to the naming of your pcap files and the corresponding TLS-keys files, you could create a script/batchfile that takes the common denominator as an argument and starts wireshark reading the pcap file with -r <filename of pcap file> and selection the TLS-keys file with the option -o tls.keylog_file:<filename of keys file>