[p4] Using p4 protect to create a "public" user
quanah at zimbra.com
Wed Oct 10 19:40:15 PDT 2007
I'm trying to set it up so I can have a user named "public" read just one
particular part of the perforce tree. I've got this mostly working, except
for three issues.
(1) The user can change their password. Since I want to make this user
generally available, I need that capability blocked.
(2) The user can see the change lists for all branches (p4 changes -i -l is
particularly problematic). How can I limit it so that p4 changes only
shows those changes in the view it is allowed to see?
(3) I'd like it so that the user cannot change the P4CLIENT view it uses
Current protections are:
list user public * -//...
list user public proxy-10.10.140.42 -//...
read user public proxy-10.10.140.42 //depot/public/...
i.e., the public user is only allowed to read when using the internal
proxy. All other access is denied. Thanks in advance for any pointers. :)
Principal Software Engineer
Zimbra :: the leader in open source messaging and collaboration
More information about the perforce-user