You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Claudio Ochoa <co...@fi.upm.es> on 2005/08/23 09:02:59 UTC
svnserve question
Hi, we have several users in our system and all of them connect to the
main repository using svnserve thru svn+ssh://
However, we have also some non-system users to whom we would like to
grant read-only access, so they can access thru svn://
The problem I face is that authenticated users in the svnserve.conf file
includes both system and non-system users, so if auth-access is set to
read, system users will not be able to write...
Is there any way to differentiate between system and non-system users,
in order to grant read-write and read-only access to them, respectively?
I know I could do it by setting Apache, but I want to know if this is
possible with svnserve, or if it will be possible in the future.
We are not interested in allowing read-only anonymous access, since we
want to keep track of the people accessing to the rep.
Any help will be appreciated.
Thanks
Claudio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnserve question
Posted by David Anderson <da...@calixo.net>.
Claudio Ochoa wrote:
>> Soon, this should also be possible at a finer grained level,
>
> David, thanks for your answer. How soon is soon?
Soon as in "the patch which implements it has just been posted for
review on the development mailing list". I have no voice in what goes
into which release, but I'd expect the feature to be scheduled for
1.3.0, whenever that is due to happen.
> Basically, our system users use svn+ssh since that allow us not to send
> cleartext passwords. Besides that, we want to allow non-system users to
> read-only access our rep, without having to create a system account for
> them, and without allowing anonymous access. This is the reason I
> thought using svn would help us. I don't know if this answer your question.
Yes and no. Like I said in my rant, svn:// doesn't actually send any
usable password token in cleartext. That's why the passwords are stored
in cleartext on the server - so as to allow an authentication protocol
that does not reveal an authentication token usable in a replay or plain
password theft attack.
svn+ssh doesn't add any security in that respect; what it does provide
is the capacity to plug into lots of auth systems (which svn:// doesn't
do yet), and to have a digital certificate for the server (which svn://
also doesn't do yet). Other than that, you could just set up plain svn
access, with the pre-commit hooks I spoke of, and sit and wait for authz
to come along in a future release. Depends on what you need.
- Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnserve question
Posted by Claudio Ochoa <co...@fi.upm.es>.
David Anderson wrote:
> Claudio Ochoa wrote:
>
> As of today you can hack what you want into svnserve, using pre-commit
> and pre-revprop-change hooks. The commit author can be looked up in the
> transaction via svnlook. You can therefore look the name up, either in
> the svn passwd store or the system store, to decide in which category
> the user is in, and appropriately deny access at that level.
>
> Soon, this should also be possible at a finer grained level,
David, thanks for your answer. How soon is soon?
> Also, on a side note, I'm a little perplexed about why you want to
> restrict write access to only one of the two repository access methods.
> What is the rationale behind that?
Basically, our system users use svn+ssh since that allow us not to send
cleartext passwords. Besides that, we want to allow non-system users to
read-only access our rep, without having to create a system account for
them, and without allowing anonymous access. This is the reason I
thought using svn would help us. I don't know if this answer your question.
> Sorry for all this extra text, I felt like ranting a little :-)
No problem at all, if it helps me to fix my problem! thanks!
Claudio
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svnserve question
Posted by David Anderson <da...@calixo.net>.
Claudio Ochoa wrote:
> Is there any way to differentiate between system and non-system users,
> in order to grant read-write and read-only access to them, respectively?
As of today you can hack what you want into svnserve, using pre-commit
and pre-revprop-change hooks. The commit author can be looked up in the
transaction via svnlook. You can therefore look the name up, either in
the svn passwd store or the system store, to decide in which category
the user is in, and appropriately deny access at that level.
Soon, this should also be possible at a finer grained level, because of
the addition of path-based access control support to svnserve, which
would allow you to define a group of system users and a group of svn
users (listed in the svn passwd file) and attribute different access
credentials to each group.
Also, on a side note, I'm a little perplexed about why you want to
restrict write access to only one of the two repository access methods.
What is the rationale behind that? Off the top of my head, I can see
one reason you might want to do this, which relies on some inaccurate
assumptions. My anticipated apologies for my jumping to wrong
conclusions if you are motivated by something completely and utterly
different, in which case I'd be interested to hear about it.
The base I'm thinking of is "Writing should go over ssh for added
security". This argument is essentially moot, because the changes are
still leaked in cleartext over the network by someone updating their
working copy via svn://. Also, the password is not sent in plaintext
via svn://, contrary to somewhat of a popular belief. So, if you're
offering svn:// access anyway, there is no real advantage to also having
svn+ssh://, except for the alternate authentication possibilities
brought on by PAM, which you don't seem to really be using here.
Some hosting providers offering subversion repositories (eg. BerliOS
developer) put up both svn and svn+ssh access methods, but have a
different reasoning as far as I understand:
- their svn access is completely read only, and is aimed for anonymous
tracking of the repository.
- their svn+ssh access is used for authenticated commits, because
(a) it allows them to use things like pam_*sql or pam_ldap and store
users/projects in more maleable data stores than flat files, and
(b) it is "user-interface" consistent with cvs+ssh, which is the
only way I know to commit without leaking passwords in cleartext with a
stock CVS. This helps people ease themselves into "that new cvs thingy"
with minimum transition pains. Essentially, a historical reason.
Sorry for all this extra text, I felt like ranting a little :-). Feel
free to ignore any or all of this if you don't really care.
- Dave.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org