MyDLP Blog

easy, simple, open source data leakage prevention

Archive for the ‘HowTo’ Category

MyDLP Howto in Russian

with 4 comments

Now, MyDLP Installation HowTo is in Russian. We love our contributors :) .

Very special thanks to

Written by kerem

March 22nd, 2011 at 1:27 pm

Posted in HowTo,News,Russian

MyDLP HowTo in Vietnamese

without comments

Thanks to, MyDLP Installation Howto is now in Vietnamese.

You can check out this document from here:

Written by kerem

March 22nd, 2011 at 1:26 pm

Posted in HowTo,News,Vietnamese

MyDLP on HowtoForge

without comments

A howto about installing and using MyDLP has been published on

Check it out :)


Written by kerem

March 17th, 2011 at 9:38 pm

Posted in HowTo,News

How to install MyDLP?

with 5 comments

MyDLP is not just a network server, only a part of MyDLP is.

We define MyDLP as a complete Data Loss Prevention solution. Therefore, installation of a complete solution is a bit different than a network server. But, not harder.

To implement DLP in 30 minutes, check out these documents;

For others and future documents, click here.

Written by kerem

November 30th, 2010 at 11:13 am

Posted in HowTo

MyDLP Auto Distribution

without comments

Another new extensive feature from MyDLP.

In almost every DLP installations, system administrators seek for a way to load balance DLP solutions and this process generally become painful because of synchronization and redundancy issues.

MyDLP Team introduced the feature Auto Distribution which enables system administrators to create an active-active cluster within minutes.

Check out our new document about Auto Distribution for details.

Written by kerem

November 30th, 2010 at 11:05 am

Now squid3-ssl packages in MyDLP repository

with 2 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