to handle permissions like standard svnserve ?
investigate this point yet.) Recommendations, 4th bullet “If you have an existing infrastructure heavily based on SSH accounts” > If your deep desire for encrypted communication still draws you to > this option, we recommend using Apache with SSL instead. I would add “or use the svn+ssh method with a shared ssh account and pubkeys listed in authorized_keys” I would add the following recommendation: (not that I experienced it, but it is obvious that it is dangerous) If using svn+ssh, choose either the method using one ssh account for each user, or the one using pubkeys in authorized_keys, but don’t mix them – oh no, don’t. Tunneling over SSH: should distinguish the 2 cases defined above. Cheers — Eric ——————————————————————— To unsubscribe, e-mail: dev-unsubscribe@… For additional commands, e-mail: dev-help@…
