Wireshark cert11/21/2023 # enable https on port 443 with snakeoil certificates Since they are self-signed, they will not be recognized as trusted certificates by most user-agents but that is not a problem here. These are self-signed certificates that can be used for testing. Additionally, we enable TLS encrypted connections on port 443 and for that we use the snake oil certificates provided by the ssl-cert package. This sets up an Apache httpd webserver that accepts plain-text connections on port 80 by default. To run the Apache httpd container, create a file called Dockerfile with the following contents. We will run Apache httpd inside a Docker container for convenience but it would work just the same for non-containerized Apache httpd installations, whether they are installed from the distro’s software repository or self-compiled. First, we run a simple Apache httpd server that accepts plain-text connections on port 80 and TLS encrypted connections on port 443. To start off, let us look at an example, of how we can debug HTTP traffic with tshark. The debugging shown here can of course be done using the GUI-based Wireshark as well. Tshark is the CLI-based version of Wireshark and provides more or less the same capabilities for dissecting network packets. In this case it is easy enough to use a tool like tcpdump to capture the packets and inspect them with a tool like Wireshark.įor the demonstrations below, tshark is used instead of Wireshark. This is trivial when HTTP requests are sent over an unencrypted channel. To debug HTTP requests, it may be useful to capture traffic and look at the packets that are sent back and forth between the client and the server. This entry was posted in Security and tagged apache security ssl tcpdump tls tshark wireshark on by Simon Studer
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |