How can I protect my PHP script?

Anon

I have a question about how to prevent others steal my PHP code? Let say I help a company to write a intranet php system and stored in their server. How can I prevent this company's programmer to steal/maint my code without my permission.

Anon

No.

You can put "copyright bladebla" at the bottom, so you can sue them if you find out they stole it, but you can't stop them from reading/stealing your code.

Apart from that, is you help a company to write code and they pay you to do it, they are effectively buying the code.

Anon

You could wait for zend to release their PHP 'encoder':

http://www.zend.com/zend/products.php

Dan.

Anon

I doubt if any paying customer would accept this.

If someone hires a programmer to develop some software, they will expect (read "suew your ass if you fail to deliver") the source code as well as executable.

Cheers,

Jack Healy

www.combustion.ie
Check out our Free HoHoHosting offer!

Anon

Thx Vincent and Dan Zambonini.

Vincent,
Thx for your help!!! Most of my questions are answered by u!!! However, I want to point out that if I write PHP script for a company is different than writting a pgm with C/C++ because these C/C++ pgm had to have complied and others cannot alter it without my permission. BTW, I think the company cannot own the code, they can just own the s/w licence.

Thanks,
Ray

Anon

It is all down to how you draw up the contract.

If they hire you to help to write some code, then they own the code.

If they ask you to write a program for them, then you can sell them just the software license.

Anon

Yes, I agree with u

Anon

There's a difference between custom-made software and "off-the-shelf" products.

If I buy Microsoft Office:
I only buy a licence to use it
I don't get access to the source
The whole thing costs me a few hundred dollars.

If I commission a team of programmers to write an office suite with similar functionality from scratch:
I own the software
I own the source
The whole thing costs me many millions of dollars

A good rule of thumb is that if you are paid to develop software, then whoever pays you owns the software.

However, you and your customer can agree different terms if you like. For instance:

you might offer to do the work for less if they don't get the source and have to go to you for any enhancements.
(If the customer agrees to this, he is an idiot. He's fu*ked if you get run over by a bus)
you might offer to do the work for less if you retain the rights to the product so that you can sell it again and agin to other customers - but your customer can also do what he likes with source
(much better for everyone)

Regards,

Jack

Anon

If I commission a team of programmers to write an office suite with
similar functionality from scratch:
I own the software
I own the source

A good rule of thumb is that if you are paid to develop software, then
whoever pays you owns the software.

Not necessarily; it depends on the legal jurisdiction. Maybe it's true in your_locality, but in the USA the default (i.e. absent a specific clause in a contract specifying otherwise) is: if it's created by an employee, it belongs to the employer; if it's created by a non-employee it's owned by the creator. (You and I doubtless agree on the wisdom of a business person contracting for development without getting ownership of the resultant code, but that's a different matter.)

Anon

Hello,
How can I use Seagate Crystal Reports with PHP.

Thanks