You (olivares) are not allowed to access to (crontab) because of pam configuration.

[Antonio Olivares]

Dear fellow testers,

It has been a while and I have been having troubles editing my crontab.

Even root cannot access it :(

This is telling me something.  I wonder what I need to do to get this fixed.


[root@riohigh ~]# crontab -l                                                    

Authentication service cannot retrieve authentication info
You (root) are not allowed to access to (crontab) because of pam configuration.
[root@riohigh ~]# exit                                                         
logout                                                                         



[olivares@riohigh ~]$ /etc/pam.d/system-auth
bash: /etc/pam.d/system-auth: Permission denied
[olivares@riohigh ~]$ su -                     
Password:                                      
[root@riohigh ~]# cat /etc/pam.d/system-auth
#%PAM-1.0                                   
# This file is auto-generated.              
# User changes will be destroyed the next time authconfig is run.
auth        required      pam_env.so                             
auth        sufficient    pam_unix.so nullok try_first_pass      
auth        requisite     pam_succeed_if.so uid >= 500 quiet     
auth        required      pam_deny.so                            

account     required      pam_unix.so
account     sufficient    pam_localuser.so
account     sufficient    pam_succeed_if.so uid < 500 quiet
account     required      pam_permit.so                    

password    requisite     pam_cracklib.so try_first_pass retry=3
password    sufficient    pam_unix.so sha512 shadow nullok try_first_pass use_authtok     
                                                                     
password    required      pam_deny.so                                           

session     optional      pam_keyinit.so revoke
session     required      pam_limits.so        
session     [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid   
                                                                     
session     required      pam_unix.so                                           
[root@riohigh ~]# /etc/pam.d/crontab                                            
-bash: /etc/pam.d/crontab: No such file or directory                            
[root@riohigh ~]# cat /etc/pam.d/crontab                                        
cat: /etc/pam.d/crontab: No such file or directory                              
[root@riohigh ~]# dmesg | grep 'avc'                                            
You have new mail in /var/spool/mail/root                                       
[root@riohigh ~]# exit


Thanks for any help/advice/suggestions which are offered to see if this problem goes
away.

Regards,


Antonio

[Kevin Kofler]

Antonio Olivares wrote:
>  It has been a while and I have been having troubles editing my
> crontab.
>  
>  Even root cannot access it :( 
Disable SELinux?

        Kevin Kofler

[Frank Murphy]

Kevin Kofler wrote:
>  Antonio Olivares wrote:
> > It has been a while and I have been having troubles editing my crontab.
> >
> > Even root cannot access it :(
>  
>  Disable SELinux?
>  
>          Kevin Kofler
>   
I also had this "su\sudo setenforce 0" will fix it,
then create a local policy using audit2allow.
Actually, I've just reported it, just a few minutes ago.
https://bugzilla.redhat.com/show_bug.cgi?id=492711

Frank

[Bill Crawford]

On Saturday 28 March 2009 17:03:34 Frank Murphy (Frankly3D) wrote:
>  Kevin Kofler wrote:
>  > Antonio Olivares wrote:
>  >> It has been a while and I have been having troubles editing my crontab.
>  >>
>  >> Even root cannot access it :(
>  >
>  > Disable SELinux?
>  >
>  >         Kevin Kofler
>
>  I also had this "su\sudo setenforce 0" will fix it,
>  then create a local policy using audit2allow.
>  Actually, I've just reported it, just a few minutes ago.
>  https://bugzilla.redhat.com/show_bug.cgi?id=492711 
Or, use "crontab -e" which is the intended method.

[Frank Murphy]

Bill Crawford wrote:
>  On Saturday 28 March 2009 17:03:34 Frank Murphy (Frankly3D) wrote:
> > Kevin Kofler wrote:
> >> Antonio Olivares wrote:
> >>> It has been a while and I have been having troubles editing my crontab.
> >>>
> >>> Even root cannot access it :(
> >> Disable SELinux?
> >>
> >>         Kevin Kofler
> > I also had this "su\sudo setenforce 0" will fix it,
> > then create a local policy using audit2allow.
> > Actually, I've just reported it, just a few minutes ago.
> > https://bugzilla.redhat.com/show_bug.cgi?id=492711
>  
>  Or, use "crontab -e" which is the intended method.
>   
Been there done that, same result. "Not Allowed",
prior to audit2allow