MyDLP Blog

open source data leak prevention

Now squid3-ssl packages in MyDLP repository

without comments

Everybody who played with Squid on Ubuntu, have probably encountered with this problem; Ubuntu Squid packages had been compiled without SSL option. Therefore, it is not possible to proxy HTTPS connections with Squid on Ubuntu Server.

So, what should we do in order to overcome this?
If I compile Squid from original source tree, I will be forced to follow new releases and security updates for Squid manually. APT will become useless for me.
If I get dpkg source of Ubuntu Squid package with apt-get source squid3, change debian/rules, add --enable-ssl to configure, recompile it and deploy it instead of original Ubuntu Squid package (as explained here), SSL support will dissappear after installing first update for Squid from official Ubuntu repository.
We have solved all these by creating a new package named squid3-ssl. squid3-ssl replaces squid3, conflicts with squid3 and provides squid3 (dpkg terms). In other words, both squid3 and squid3-ssl could not be installed together, you could install squid3-ssl instead of squid3 and this situation will not cause any dependency problems.
Furthermore, these packages will be automatically compiled after any update for Squid in official Ubuntu repositories and deployed into MyDLP Ubuntu repository.
As a result, adding MyDLP repository and installing squid3-ssl package, will provide Squid SSL functionality without challenging any of the problems I have mentioned above.
To use and install squid3-ssl packages;
Add this line to /etc/apt/sources.list ;

deb lucid/

Then, call aptitude to update itself and install squid3-ssl ;
sudo aptitude update
sudo aptitude install squid3-ssl
That’s all…
Have a good day :)

Written by kerem

November 8th, 2010 at 6:50 pm

Posted in HowTo,Squid,Ubuntu

Leave a Reply