RE: cron vs. anacron

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> From: Moray Henderson [mailto:Moray.Henderson@xxxxxxxxxxxxxxxx]
> Sent: 13 February 2012 13:05
>
> Can someone explain why the logwatch process run by crond transitions
> to unconfined_t, while the same process run by anacron remains in
> logwatch_t:s0-s0:c0.c1023?

Does this answer my own question?

[root@centos services]# ldd /usr/sbin/crond
        linux-gate.so.1 =>  (0x00550000)
        libselinux.so.1 => /lib/libselinux.so.1 (0x00671000)
        libpam.so.0 => /lib/libpam.so.0 (0x001c8000)
        libpam_misc.so.0 => /lib/libpam_misc.so.0 (0x00803000)
        libaudit.so.0 => /lib/libaudit.so.0 (0x00a2e000)
        libc.so.6 => /lib/libc.so.6 (0x0031c000)
        libdl.so.2 => /lib/libdl.so.2 (0x00110000)
        libsepol.so.1 => /lib/libsepol.so.1 (0x00bb0000)
        /lib/ld-linux.so.2 (0x00eef000)
 [root@centos services]# ldd /usr/sbin/anacron
        linux-gate.so.1 =>  (0x005d3000)
        libc.so.6 => /lib/libc.so.6 (0x0014d000)
        /lib/ld-linux.so.2 (0x00129000)

Am I right that crond can do type transitions because it was written with
libselinux.so in mind, while anacron can't because it wasn't?  Although
somehow my ps process did manage to get to logwatch_t.

Am I right that that was a bug?  Looks like it's been fixed in CentOS 6.
Unfortunately I'm stuck on 5 for this project.  I'll have to come up with a
workaround.



Moray.
"To err is human; to purr, feline."




--
selinux mailing list
selinux@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/selinux



[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux