Tim: >> By the way, that's not the fault of SELinux. It's the fault of those >> who put software on a system using SELinux without doing it properly. Beartooth: > Oho! I also got an email under the list, identifying it as a > bug : > > https://bugzilla.redhat.com/show_bug.cgi?id=451560 > > Such being the case, I beg SELinux's pardon. As I found out back then, but forgot about in the meantime, it's the DHCP client making the classic user blunder (*) when moving/copying files about, as it swaps the backup and current configuration files around. With filename/location based creation of SELinux contexts, in the first place, you have to create a file in the right place, and with the right filename, for it to be given the right context. If you create it elsewhere, then move it over, it'll have the wrong contexts. * User create's some file in the homespace, then moves it over to /etc/ or their webserver, and it won't work, because it still has their default user contexts. -- [tim@localhost ~]$ uname -r 2.6.25.9-76.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
