[Serdev] CVS module contrib

[Cesc Santasusana]

If TLS was a standalone process running independently ... but it is too 
integrated (for me), to place it somewhere else ... but hey, this is just my opinion.
I do not see why it should be separated from the core SER. 
If you are worried that for paying costumers it gets messed up, it can be 
place in /tls_free folder, then before compile just needs a soft link like:
> ln -s ser_tls tls

As long as people know about the existence of TLS code for SER and 
know how to find it (a mention in the webpage then would be of first order relevance), 
it is good with me.

my 2 cents ...

Cesc


Unclassified


>>> Andrei Pelinescu-Onciul <andrei at iptel.org> 06/06/05 02:07PM >>>
On Jun 06, 2005 at 13:14, Cesc Santasusana <cesc.santasusana at nl.thalesgroup..com> wrote:
> It is a good idea ... 
> 
> One of the first ones could be TLS-free stuff ... i have improved it a little bit more
> (more configuration options from the script file not used in the first releases) and 
> some fixes to make it compile in openssl v0.9.6 (tested on 0.9.7 and 0.9.6, i have
> not tried earlier version ... anyway they'd better not be used).
> 
> Even better would be to include it by default in its original folder ( ...../tls ), but 
> if what it takes to be included and mantaiined somehow other than by hand is 
> to be put in the contrib module ... so be it.

I would suggest to have it separatley in a /ser_tls dir at the same
level as ser and rtpproxy.

A user would have to check it separately in his sip_router tree and mv
ser_tls tls. He would need to do this only the first time.


Andrei