since the 2004.1 changes, /etc/.pwd.lock is labeled system_u:object_r:shadow_t, instead of system_u:object_r:etc_t unfortunately, cvs is trying to read that file in most cases. this means allow { sysadm_t staff_t user_t } shadow_t:file { read }; which ain't good. even if I use SystemAuth=no the problem remains. what would be the best resolution of this? the patch of cvs sources, a cvs_t domain, or a patch of the current policy?
mea culpa. invalid bug. i'm tired.