Currently svn+ssh is what is active but that requires an active shell account on the svn server - clearly not a good thing when non-OSAF people need commit privs. Also svn+ssh allows access to all the repositories that are on the server with no way to easily mix and match write privs based on the project.
The built-in authentication that svn uses allows for the different permissions and it will also cache the password the first time you use it so that's not too bad. But I plan on having a test repository up tomorrow so people can try it out so I can get some feedback.
--- Bear http://code-bear.com Open Source Applications Foundation (OSAF) http://www.osafoundation.org PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 On May 23, 2005, at 8:35 PM, Grant Baillie wrote:
On May 20, 2005, at 3:52 PM, Mike Taylor wrote:I will be converting the CVS repository to SVN this coming Wednesday, May 25th. The conversion will occur early in the day my time (EST).What this means is that CVS will become read-only and the code base will be moved to the subversion repository. As it stands now all of the CVS history and tags and the like will be transferred.The change impacts many small parts of our dev environment. CVS userid and passwordThe SVN userid and password should be the same - the actual details of that will be known later when I do a test-run of the security changes.Are we going with http(s) + a password to access the repository, or svn+ssh?I'm a fan of the latter, since then I don't have to store the password in plain text anywhere on the system (or have to type it every time).--Grant _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
PGP.sig
Description: This is a digitally signed message part
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "Dev" mailing list http://lists.osafoundation.org/mailman/listinfo/dev
