On Mon, Feb 6, 2012 at 2:49 PM, PS <
packe...@gmail.com> wrote:
> I guess I may be doing it wrong. I tried to use the .pem file for "
xyz.com" in wireshark and I was unable to decrypt the traffic. I am not sure if it is due to the key file options. I am using the following: 192.168.2.1, 3128, http, "key.pem". Since squid is running on 192.168.2.1 port 3128. I will try it again to see what I where I am messing up.
>
> As for using ICAP for ClamAV, I think I can enable icap on the squid server and forward ALL of the request to clamv so that I can sniff the unencrypted packets being sent to clamv. Problem is that I don't think that it would be a good idea to have every single request go to ClamAV just for me to sniff the traffic.
>
> I will try the wireshark approach again and then go from there. Thank you!
>
> On Feb 6, 2012, at 2:22 PM, Will Metcalf wrote:
>
>> If you are using sslbump/dynamic ssl inside of squid nothing is
>> preventing you from using the .pem files along with the index file
>> ssl_crtd produces for use in wireshark etc. You should adjust the size
>> of the DB accordingly. This would allow you to decrypt traffic going
>> to from/your proxy if you have rotating packet capture. That said I
>> don't know of anything that does exactly what you are talking about.
>> Closest thing I've seen is AV scanning with eCAP/ClamAV in conjunction
>> with sslbump/dynamic ssl.
>>
>>
http://www.e-cap.org/Downloads
>>
>> Regards,
>>
>> Will
>>