Partha added a comment - 19/May/2009 11:41 PM Dear Raghu, We do not view this as a major security issue. As pointed out by Jamie on the forums, you should have configured the svn user/pass to be a system account with read only access, rather than your own user/pass. Once your box is compromised - i.e. someone gets filesystem access, then you are out of luck. We need access to the plain text password for svn, because we need to pass that value to svn. Any 'encryption' would be pretty worthless because the secret would have to be shipped in the application. Normally passwords are one way encrypted, i.e. you can never get the plain text value back, you can only check to see if you have one that matches, however in this case we need the plain text value of the user/pass, so one way encryption is not possible. For my view, it is a serious issue because the SVN repository I configure is my LDAP password. If some one opens that file, they can access any system with that LDAP password and they can do anything on my account. I can't restrict the file system, because some of my team member need an access. As pointed out by Jamie, you should not configure your LDAP user/pass for the svn repository, but instead configure a system account that has minimal access (read only to svn repository). Kind Regards, Partha Kamal