Dominick Grift (domg472)

Dominick Grift Stefano Canepa

@scanepa because there were some issue reported with regard to mislabelled files.

Dominick Grift Stefano Canepa

@scanepa After installation do: 1. restorecon -R /var 2. yum install policycoreutils-restorecond; restorecon -R ~, and relogin.

Dominick Grift

@ardrigh alright thats the first fix, there should be more issues, please test/reproduce

Dominick Grift

@ardrigh Yes /var/lock symlink is mislabelled , suggested fix in report wont fix it i believe. Maybe restorecon -R -v /var will...

Dominick Grift

@ardrigh Actually restorecon -R -v /var...

Dominick Grift

@ardrigh The symbolic link is mislabelled. try restorecon -R -v /var/lock; ls -alZ /var | grep lock (should be var_lock_t)

Dominick Grift

@ardrigh you can also find it by looking at the ino= in the avc denials then: find / -inum $ino

Dominick Grift

@ardrigh it could also be that the pppd init script now creates the lock files

Dominick Grift

@ardrigh If that is true then all we have to do is add file context specs for pppd's lock file (there is non currently)

Dominick Grift

@ardrigh i suspect that something later runs restorecon over them and resets the types to the type of the parent (var_lock_t)

Dominick Grift

@ardrigh When pppd creates its lock files in /var/lock.* they (should) get created with type pppd_lock_t type

Dominick Grift

@ardrigh Are you also seeing the SELinux pppd issue? Can you tell me which files pppd stores in /var/lock exactly, and where?

Dominick Grift Adhidarma Hadiwinoto

@adhisimon "System settings" > "Default applications" > "Web"