As previously discussed, we need to extend this functionality.
How do we achieve this? Tracing system calls turned out to be partially insufficient due to the data being already encrypted by the point they reach the corresponding write(2) or send(2) system call.
Well one way I could imagine doing this would be with LD_PRELOAD, write a dummy library that implements the numerous SSL functions such as SSL_write(3), SSL_read(3), SSL_recv(3), SSL_send(3) etc. Recording the data being exchanged before routing them back to their original destination.
@zvr You've talked about setting up a proxy server before, is that what you were thinking or perhaps something else? Let me know.
As previously discussed, we need to extend this functionality.
How do we achieve this? Tracing system calls turned out to be partially insufficient due to the data being already encrypted by the point they reach the corresponding
write(2)
orsend(2)
system call.Well one way I could imagine doing this would be with
LD_PRELOAD
, write a dummy library that implements the numerous SSL functions such asSSL_write(3)
,SSL_read(3)
,SSL_recv(3)
,SSL_send(3)
etc. Recording the data being exchanged before routing them back to their original destination.@zvr You've talked about setting up a proxy server before, is that what you were thinking or perhaps something else? Let me know.