@@ -9,7 +9,7 @@ This demo was created to accompany the "Debugging with eBPF Part 3: Tracing SSL/
99You must have the BCC development package installed. On Ubuntu, the package can be installed as follows:
1010
1111```
12- sudo apt install libbpfcc-dev
12+ sudo apt install libbpfcc-dev binutils clang llvm bcc python3 openssl -y
1313```
1414
1515Other distributions have similar commands.
@@ -29,34 +29,26 @@ A demo application to trace is included. It is a simple client-server written in
2929First, you'll have to generate some certificates for the client and server.
3030To keep things simple, you can generate some self-signed certificates as follows:
3131
32- ```
33- make -C ssl_client_server certs
34- ```
3532
36- To run the demo app , you'll need two terminals.
33+ To run the demo, you'll need two terminals.
3734
38- In one terminal, run the server:
35+ In one terminal, open a secure connection to e.g. google
3936
4037```
41- cd ssl_client_server; ./server.py
38+ openssl s_client -connect google.com:443
4239```
4340
44- In the second terminal, run the client:
41+ In the second terminal, run the tracer on the ProcessID (pid) of the above connection
4542
4643```
47- cd ssl_client_server; ./client.py
44+ sudo ./openssl_tracer $(pgrep -f openssl)
4845```
49-
50- ## Run Tracer
51-
52- The BPF tracer is run as follows:
53-
46+ Now, back in the openssl terminal
5447```
55- sudo ./openssl_tracer <pid>
48+ GET / HTTP/1.1
49+ and press enter twice
5650```
5751
58- To run it on the demo app, run the following command in a separate terminal:
5952
60- ```
61- sudo ./openssl_tracer $(pgrep -f "./client.py")
62- ```
53+
54+
0 commit comments