Project security

[MuadDubby]

Hi -

Serious problem over here. I have, for example, a source safe database with one user (named "aaa&quot configured to use it. Under Source Safe admin, I give this user check in/out acces.

Now what happens when this person tries to check things in/out: windows will access the database folders (and shadow folders if applicable) and try to update files using the account name of the person currently logged into the network at the moment (in our case, "aaa&quot. So this network account must have read/write access to the database folder.

My question is - what is stopping the user from going through DOS or Explorer, and deleting the database directory? Can I prevent this somehow?

Please answer ASAP. Thank you.

 

[TomasDill]

No. We just make each night backup copy of our server, that is partial measure for the case you mentioned.

Vlad Grynchyshyn
vgryn@softserve.lviv.ua

http://www.softserve.lviv.ua

The professional level of programmer could be determined by level of stupidity of his/her bugs

 

[MuadDubby]

Thank you, that is what I thought. All the Microsoft documentation seems to say this as well. Pretty unsecure for a version control system, I think.

 

[TomasDill]

Remember that this is for your development team, where probably everyone trust each other. Do you have so large team that can expect intruders/hackers/spoilers? I think for such large projects (and such large teams) it will not be a problem for you to make backup each hour ;-) for small teams it is just not needed...

Vlad Grynchyshyn
vgryn@softserve.lviv.ua

http://www.softserve.lviv.ua

The professional level of programmer could be determined by level of stupidity of his/her bugs

 

[MuadDubby]

The problem I am having is not with a lack of trust, but rather with the avoidance of accidents. The group of developers is small, but the database is very large (thus making an hourly backup impossible). A nightly backup is being performed, but I just wanted to see if it could be made more secure. Oh well.