Simple: don't give the developers access to the VSS database share if they don't need it. For developers who need to have access, it will be hard to prevent them from copying the sources (e.g. you can't strip-search them daily to see if they don't have a usb flash drive on them, can you )
It's the same for the big companies. For instance, I don't have access to Windows or Office source code, the same way as someone in Office doesn't have access to VSS code. I do have access to VS and VSS sources, and I could copy them, but I don't want to do that. That's where contract rules, employee's handbook, employee's honesty, the job, police/fbi and lawyers come into place... :-)
Sorry, I can't tell you what's in Microsoft employee handbook.
I'd advise talking to a lawyer when writing your company's handbook or job offers. When an employee accepts a job he can sign for instance that he'll respect the handbook rules, or else he may lose his job and support the consequences in acccordance with existing laws.
I'm not sure what you're trying to do, but VSS may not be the answer.
VSS doesn't have security measures that will prevent a developer to steal source code and publish it outside your company (copy/mail).
You can prevent other users to access the files stored in VSS databases by setting correctly the Windows permissions on the database's file share and the NTFS permissions on the files. You can't prevent developers that have granted access to the database from copying the source code stored in the database.
How to protect company systems source code?
Codoc
Simple: don't give the developers access to the VSS database share if they don't need it. For developers who need to have access, it will be hard to prevent them from copying the sources (e.g. you can't strip-search them daily to see if they don't have a usb flash drive on them, can you )
It's the same for the big companies. For instance, I don't have access to Windows or Office source code, the same way as someone in Office doesn't have access to VSS code. I do have access to VS and VSS sources, and I could copy them, but I don't want to do that. That's where contract rules, employee's handbook, employee's honesty, the job, police/fbi and lawyers come into place... :-)
Alin
HexKrak
Sorry, I can't tell you what's in Microsoft employee handbook.
I'd advise talking to a lawyer when writing your company's handbook or job offers. When an employee accepts a job he can sign for instance that he'll respect the handbook rules, or else he may lose his job and support the consequences in acccordance with existing laws.
Alin
mschai
MS was not my intention.
Anyhow thank you dear.
exoloner
I'm not sure what you're trying to do, but VSS may not be the answer.
VSS doesn't have security measures that will prevent a developer to steal source code and publish it outside your company (copy/mail).
You can prevent other users to access the files stored in VSS databases by setting correctly the Windows permissions on the database's file share and the NTFS permissions on the files. You can't prevent developers that have granted access to the database from copying the source code stored in the database.
Alin
Guennadiy Vanine
ZafarIqbal
Alin,
I am interested to read what is written in the employee’s handbook regarding what we talked about, can you send me something
Email: adsc@adsc.net
richard luo
Thank you Alin for your reply.
Then how the big companies protect their rights
This means if I employed 5 more developers in the company, I can’t prevent them from copying any system source code !!