[p4] Multiple clients - single user

DAVID Foglesong defoglesong at msn.com
Sun Jun 17 11:28:55 PDT 2007


>From: Didster <didster at gmail.com>
...
>But...  Not every "company" in the world takes software theft
>seriously - and it just seemed to me that it's a strange decision to
>make the license based on per-user rather than per-client when sharing
>a user technically is possible and presents no problems from a
>functional point of view - hence my question.

Beyond the legal aspects, there are some real functional issues with using a 
single shared account. The most glaring one is that you have effectively no 
security. Since there's only one account, everyone has "super" access to the 
system.

That means anyone can:
- Run obliterate to permanently remove data from the system.
- Edit the protect or trigger or typemap table.
- Change (or delete) any label or client or branch spec. (Setting the 
"locked" option won't matter if you only have one account that owns all 
specs.)
- Set a password on the single shared account and lock out everyone else.

Having a single shared account will also make review daemons and 
bug-tracking (p4dti/jobs) pretty much useless.

I doubt a 4-person shop would encounter this situation, but I can't imagine 
what a SOX or ISO compliance audit would think about using a single shared 
account for all changes made to the system.

_________________________________________________________________
Don’t miss your chance to WIN $10,000 and other great prizes from Microsoft 
Office Live http://clk.atdmt.com/MRT/go/aub0540003042mrt/direct/01/


More information about the perforce-user mailing list