> What do the rest of you do, its a hard one. the best you could do from a legal standpoint is make sure the contract you have with the customer clearly states the ownership of IP etc so that if they do reuse it then they'll be liable.
What we do is instead of selling solutions which we give to the customer, we sell services. so all our services are hosted on our servers and the bits that we don't want to give customers source read access to, we lock down. we state this in our t&cs and contracts etc. this works quite well. They're not buying software, they're buying access to the *usage* of software. btw I don't think cfdecrypt can decrypt cf5 files, although looking at the shrewm notice board, there seem to be people claiming they can (for a fee). > -----Original Message----- > From: Garry Mills [mailto:[EMAIL PROTECTED]] > Sent: 05 September 2002 10:10 > To: '[EMAIL PROTECTED]' > Subject: [ cf-dev ] .cfm enryption > > > We're rolling out a product to a customer soon, and bluntly > speaking we > don't want them to be able to copy the app onto another server. > > Know about cfencrypt, and also know about cfdecrypt and > whilst it will stop > the numpties getting into it doubt the tech department will find it as > difficult > > A google search for coldfusion dongle returns a load of links to crack > files... > > What do the rest of you do, or is cfentrpt our only option? > (oh, and I tried > CF encrypted files on a Cobalt once and it didn't seem to > work, although > thats a separate issue) > > Garry > > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > For human help, e-mail: [EMAIL PROTECTED] > -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
