3 replies to this topic

[rhossis]

Hi,

I work for a start up that develops software for investment banks. Our software is usually provided on license basis. It is a statutory requirement to have some provision for risk management regarding the software source code. One of the client's has proposed signing an agreement whereby they keep one copy of the source code locked up in their safe rather than go for an escrow agreement, a cost they indicate they wan't to avoid. Are we setting ourselves up for a sucker-punch? What are alternatives to this as I am not very sure about handing someone our source code?. :confused:

Regards,
Rhossis

[WingedPanther]

The general point of an Escrow is to keep the source code in the hands of a mutually trusted third party. Your customer simply cannot serve in that capacity. Now, having it encrypted with the key held in escrow might be an alternative that would be cheaper, but still involve a third party.

[rhossis]

Wow, thanks, I have just talked to one of the client's managers and he likes the idea for es-crowing the key

[WingedPanther]

I hope it works out :)