-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 27.02.2012 21:15, Sven Vermeulen wrote: > On Mon, Feb 27, 2012 at 09:53:41PM +0200, Cor Legmaat wrote: >>>> This is what I get with gnome-terminal: >>>>> cor@k53s ~ $ id -Z system_u:system_r:initrc_t cor@k53s ~ $ >>>>> ssh 127.0.0.1 Last login: Mon Feb 27 20:01:41 SAST 2012 >>>>> from k53s.cor.za.net on pts/1 cor@k53s ~ $ id -Z >>>>> staff_u:staff_r:staff_t > [...] > > Hmm, being in initrc_t isn't correct either; I'd at least expect it > to be xdm_t. > > Can you check the file context of your gdm binary? > > ~# ls -Z /usr/sbin/gdm > > It should be xdm_exec_t (yes, xdm_exec_t, not gdm_exec_t). If not, > set it that way (and tell me which path the binary is at so I can > update the policy). > > ~# chcon -t xdm_exec_t /usr/sbin/gdm > > If the system complains about an unknown type, make sure you have > the xserver module loaded: > > ~# emerge selinux-xserver ~# semodule -l | grep xserver ~# rlpkg > gdm ~# ls -Z /usr/sbin/gdm > > Wkr, Sven Vermeulen >
If have had problems with this myself. Making pam_selinux.so required in the gdm pam file changed it for me most of the time. Sometimes I seem to hit some kind of race condition though which requires me to restart xdm before getting the right context. It's kind of anoying... -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPS/w7AAoJEJwwOFaNFkYc598H/1BRHhw7DdQcEKlzJ/btqAhv Lx362lccBtv78JAVVuPJnE0Al+/IpKecPfB3/YVYi+x9Yg6rENqUaeGXsVvBuarh 5lWFgzV7O+AXvgI3kc7cXfG27joiWdOZ2BMd3BRv3aZ+5H+pqzwPBmeI6jightGI EK9TO/FWnCcEeKnAzlY3nbIfwZMuIYIKTp2csLdCFYf6TaYrSJJz+SeIGUUh/QeA WmHJp4Vydtm1JhIK3ceRZ9fPDzcQnDqZEUj38jB9rGtqPl4aeq25ofdP4svpr26n zLCFJo3/CeVB0kRglbaVFrmVwKYHzdFauWoHB4zS7TK8nBYbrMq1KcHssQeAiQw= =NxbC -----END PGP SIGNATURE-----
