-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/2014 01:45 AM, Dan Callaghan wrote:
Excerpts from Dan Callaghan's message of 2014-03-06 16:43:26 +1000:
Excerpts from Daniel J Walsh's message of 2014-01-03 01:46:44 +1000:
This is caused by sshd running with the wrong label, It should be
Excerpts from Daniel J Walsh's message of 2014-01-03 01:46:44 +1000:
This is caused by sshd running with the wrong label, It should be
running as sshd_t not init_t. If the executable labeled sshd_exec_t?
ls -lZ /usr/sbin/sshd
restorecon -v /usr/sbin/sshd
should fix the label.
I
Excerpts from Dan Callaghan's message of 2014-03-06 16:43:26 +1000:
Excerpts from Daniel J Walsh's message of 2014-01-03 01:46:44 +1000:
This is caused by sshd running with the wrong label, It should be
running as sshd_t not init_t. If the executable labeled sshd_exec_t?
ls -lZ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/27/2013 05:06 PM, Philip Prindeville wrote:
I’m seeing the following after an update (via yum) from F19 to F20:
time-Tue Dec 24 16:05:44 2013 type=SYSCALL
msg=audit(1387926344.492:5867): arch=c03e syscall=1 success=no exit=-13
I’m seeing the following after an update (via yum) from F19 to F20:
time-Tue Dec 24 16:05:44 2013
type=SYSCALL msg=audit(1387926344.492:5867): arch=c03e syscall=1 success=no
exit=-13 a0=6 a1=7f4e5e7afbb0 a2=20 a3=7fff44c2c550 items=0 ppid=686 pid=693
auid=4294967295 uid=0 gid=0 euid=0
Le vendredi 27 décembre 2013 à 15:06 -0700, Philip Prindeville a écrit :
I’m seeing the following after an update (via yum) from F19 to F20:
time-Tue Dec 24 16:05:44 2013
type=SYSCALL msg=audit(1387926344.492:5867): arch=c03e syscall=1
success=no exit=-13 a0=6 a1=7f4e5e7afbb0
