mainSavannah Administration - Support: sr #105200, How to grant Read-Only access to...

 
 

sr #105200: How to grant Read-Only access to CVS for some registered users

Submitter:  Eric NOULARD <erk>
Submitted:  Fri 03 Mar 2006 12:07:05 PM UTC
   
 
Category:  Source code repositories - developer access Priority:  5 - Normal
Severity:  3 - Normal Status:  Need Info
Privacy:  Public Assigned to:  mjflick
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 09 Mar 2006 12:45:38 AM UTC, comment #5: 

Access on non-standard ports is provided with no duration warranty - do not count on it in the long run :)

Out of curiosity, what did you local sysadmin answer when you told him you needed legitimate pserver/ssh access?

Sylvain Beucler <Beuc>
Mon 06 Mar 2006 08:35:08 AM UTC, comment #4: 

I did see TOR but did not try since I found it
not acceptable in an industrial environment.
I may use it at home but I do not have the firewall problem...
Nevertheless the TOR project seems REALLY interesting
to me but I'm just not ready to put it at work for now.

When I'm at workplace http://proxytunnel.sourceforge.net/
is enough and seems to me more "acceptable", since this
is a less questionable use (in my opinion though).
[that's why I really like the cvs.savannah.nongnu.org
 responding to SSH on 443]

I didn't realize non members may use the tracker,
we may switch to this way of working.

Nevertheles having the R/W CVS control for member of
a project would still be interesting for controling
which part of the SVN may be commited by which user.

I cannot ask you that feature without trying myself,
I may try homemade Savanne install in order to contribute this, I cannot guaranty that I will found the time
to try this any time soon but if I do I will come
back to you.

Eric NOULARD <erk>
Mon 06 Mar 2006 05:43:31 AM UTC, comment #3: 

In regard to your first reason, I'd suggest tor (http://tor.eff.org) (it's really nifty)

To the second, people who are not members of a project can still use a tracker.  For now, when someone is a member of a project, they have cvs access.

Michael J. Flickinger <mjflick>
Fri 03 Mar 2006 03:02:17 PM UTC, comment #2: 

There is at least 2 reason for which anon CVS is not a solution for us:

1) It doesn't work wince it use cvspserver tcp port
   which is block by our security policy
   (really hard to change)
   In fact we even use ssh authenticated access through
   our https proxy and proxytunnel
   since tcp 22 is blocked too.
   I should note that having SSH responding on port 443
   is a very nice feature I would really want you to
   support in the long term.


2) Some people deserve being member of our Savannah
   project because they must be able to use the tracker.
   We would prefer not to grant them the CVS "write"
   access (tag, commit, admin etc...)



Eric NOULARD <erk>
Fri 03 Mar 2006 02:40:43 PM UTC, comment #1: 

The only current way to do this is by anonymous CVS access; described here: https://savannah.nongnu.org/cvs/?group=tsp

You mentioned that anonymous access is not 'ok' though.  Any reason why anonymous access would not work?

Michael J. Flickinger <mjflick>
Fri 03 Mar 2006 12:07:05 PM UTC, original submission:  

Hi,
I wanted to know wether it is possible for a project
administrator to grant only read access to a
registered user (that is not using anonymous CVS).

The need is the following:

I want some users to be able to post bugs,
   eventually new tasks or assigned them but not
   to be able to CVS commit (checkout is OK)

This kind of users may be viewed as 'management users'.
This kind of permissions management may be done for
bug, task, patch, news etc...

but not seems to be possible for CVS access.

did I miss something or is there really no mean for a
registered user of a project to have restricted CVS access?

Eric NOULARD <erk>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

Only logged-in users can vote.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-03-06 mjflick Open/ClosedOpen Closed
2006-03-03 mjflick StatusNone Need Info
    Assigned toNone mjflick

Back to the top

Powered by Savane 3.13-4b48.
Corresponding source code