#!/bin/bash # run this test many times: # time bash -c 'for ((i=0; i<100; i++)); do echo "-- $i --"; bash run-test.sh || exit 1; done' set -e rm -rf temp mkdir -p temp echo "generating tests.." python generate.py echo "running tests.." for i in $( ls temp/*.ys | sed 's,[^0-9],,g; s,^0*\(.\),\1,g;' ); do echo -n "[$i]" idx=$( printf "%05d" $i ) ../../yosys -ql temp/uut_${idx}.log temp/uut_${idx}.ys done echo failed_share=$( echo $( gawk '/^#job#/ { j=$2; db[j]=0; } /^Removing [24] cells/ { delete db[j]; } END { for (j in db) print(j); }' temp/all_share_log.txt ) ) if [ -n "$failed_share" ]; then echo "Resource sharing failed for the following test cases: $failed_share" false fi exit 0 git logo'/> index : cloud-email/mitmproxy
clone of mitm proxyJames
aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/dev/sslkeylogfile.html
blob: 1826fc2ef8d6dea3fcb619c9fedfd0f0997a331c (plain) 
1
2
3
4
5
6
7
8

The SSL master keys can be logged by mitmproxy so that external programs can decrypt TLS connections both from and to the proxy.
Key logging is enabled by setting the environment variable <samp>SSLKEYLOGFILE</samp> so that it points to a writable
text file. Recent versions of WireShark can use these log files to decrypt packets.
You can specify the key file path in WireShark via<br>
<samp>Edit → Preferences → Protocols → SSL → (Pre)-Master-Secret log filename</samp>.

 Note that <samp>SSLKEYLOGFILE</samp> is respected by other programs as well, e.g. Firefox and Chrome.
If this creates any issues, you can set <samp>MITMPROXY_SSLKEYLOGFILE</samp> alternatively.
generated by cgit v1.2.3 (git 2.25.1) at 2026-02-11 23:43:25 +0000