In the case of http in wireshark, the shape of the request packet response packet (?) is revealed as follows.
That's not how https works
I found the above and tried to copy it, but it didn't work well.
Current floating environment variables
Exit the Chrome app and
Specify SSLKEYLOGFILE in the environment variable and
Even if you turn on Chrome again and connect to https site,
Nothing is written to the file in the SSLKEYLOGFILE specified in the environment variableI don't know what's wrong.
If there is any other way to analyze https packets (requests, responses) other than the above method, please let me know.
wireshark tcpdump osx macos packet
Do you try
I was wondering about this function, so I looked, but doesn't work. Now for the amhwawa nss source code and the environment variables used in the library, but firefox dibigingyong to build only be used when possible. 그리고 크롬은 암호화라이브러리를 NSS에서 BoringSSL(OpenSSL를 구글이 포크한 프로젝트)로 변경하여 더이상 이 환경변수가 쓰이고 있지 않다고 합니다.
However, if you look at the network item in the developer tool, whether it's Firefox or Chrome, you can see it in real time at the HTTP level, even if it's encrypted traffic.
Note: https://developers.google.com/web/tools/chrome-devtools/network-performance/resource-loading?hl=ko
© 2024 OneMinuteCode. All rights reserved.