On 12/29/05, Adrian Lynch <[EMAIL PROTECTED]> wrote:
> What about obfuscation? Anyone done that, pros, cons?

Pros: the mistaken feeling that your code is somehow "safe"
Cons: incredibly complex maintenance, programmer burnout, client
frustration, the hint of paranoia, to name a few

You can obsfucate, encrypt, *and* deploy sourceless (though that
defeats the purpose of encryption, natch) -- but that's a lot of
overhead for IMHO *very* little gain. You'd be better off putting that
energy into new software, improvements, or finding better clients that
you don't feel so worried about.

Imagine a client sophisticated enough to do a code review -- not a
good environment to show them you know your stuff, but a great way to
show them you don't trust them.

Imagine trying to bring in a subcontractor to help with maintenance.

If you are *that* concerned about your code, license the use of it,
retain the copyright and use it on your own machines. Or charge enough
for the software that you feel that you got what it was worth.

If you're trying to prevent client *change* to the code, your best
approach is to clearly state in the contract that you won't
support/warrant/etc code that's been changed from the release (and
back that up w/ good version control and a physical release of the
software delivered to the client or escrow).

If you're trying to prevent client *distribution* of your code, get
clear ownership in your contract and don't be afraid to enforce it.

Or open source it and don't lose any more sleep :)

> Ade
>
> -----Original Message-----
> From: John Paul Ashenfelter [mailto:[EMAIL PROTECTED]
> Sent: 29 December 2005 16:37
> To: CF-Talk
> Subject: Re: Protecting Code
>
>
> On 12/29/05, Jennifer Gavin-Wear <[EMAIL PROTECTED]> wrote:
> > Hmm .. that's a thought ..  maybe hosting a subdomain of theirs on my own
> > server would be best?
>
>
> I wouldn't waste the time encrypting the pages. It takes about 60s on
> google to find a decryption tool for cf. It also complicates your
> deployment b/c you have to encrypt everytime you push up a change --
> which may or may not be an issue for you.
>
> > -----Original Message-----
> > From: Adkins, Randy [mailto:[EMAIL PROTECTED]
> > Sent: 29 December 2005 15:20
> > To: CF-Talk
> > Subject: RE: Protecting Code
> >
> >
> > You could encrypt the pages but not a foolproof way of protecting the
> > code.
> >
> > -----Original Message-----
> > From: Jennifer Gavin-Wear [mailto:[EMAIL PROTECTED]
> > Sent: Monday, December 26, 2005 11:40 AM
> > To: CF-Talk
> > Subject: Protecting Code
> >
> > Hi ... is there any way of protecting code.  I could be installing a
> > cart application on someone's CF server and I don't necessarily want
> > them to have access to the code.
> >
> > Thanks,
> >
> > Jenny
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Discover CFTicket - The leading ColdFusion Help Desk and Trouble 
Ticket application

http://www.houseoffusion.com/banners/view.cfm?bannerid=48

Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227941
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54

Reply via email to