I'm not even sure what component I would file this bug against, but
since a few days ago, something in Rawhide is causing every ssh
terminal, console etc to get spammed with SELinux audit messages.
Simply ssh-ing to the box gives you:
$ ssh trick
Message from syslogd@trick at Mar 20 14:13:46 ...
journal:<audit-1112> pid=2038 uid=0 auid=1000 ses=2
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1000
exe="/usr/sbin/sshd"
hostname=choo.home.annexia.org addr=192.168.0.175
terminal=/dev/pts/0 res=success'
Message from syslogd@trick at Mar 20 14:13:46 ...
journal:<audit-1105> pid=2038 uid=0 auid=1000 ses=2
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=login id=1000
exe="/usr/sbin/sshd"
hostname=choo.home.annexia.org addr=192.168.0.175
terminal=/dev/pts/0 res=success'
Last login: Fri Mar 20 14:10:49 2015 from
choo.home.annexia.org
Message from syslogd@trick at Mar 20 14:13:46 ...
journal:<audit-2404> pid=2038 uid=0 auid=1000 ses=2
subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=server
fp=SHA256:5e:91:96:9b:d3:3c:42:5c:21:e8:fe:8e:4c:c6:a8:ef:cb:3f:ff:b8:e8:c8:b0:2a:a3:d9:c7:65:40:dc:7a:62
direction=? spid=2046 suid=1000 exe="/usr/sbin/sshd" hostname=?
addr=192.168.0.175 terminal=? res=success'
If someone can suggest a suitable component and what diagnostics would
be needed, I can file a bug.
Rich.
--
Richard Jones, Virtualization Group, Red Hat
http://people.redhat.com/~rjones
Read my programming and virtualization blog:
http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW