From: Russell Coker <russell@coker.com.au>
To: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: patches for xdm.te for kdm 3.3
Date: Sun, 29 Aug 2004 20:49:24 +1000 [thread overview]
Message-ID: <200408292049.24183.russell@coker.com.au> (raw)
In-Reply-To: <20040829091112.GA7610@lkcl.net>
On Sun, 29 Aug 2004 19:11, Luke Kenneth Casson Leighton <lkcl@lkcl.net> wrote:
> On Sun, Aug 29, 2004 at 05:21:55PM +1000, Russell Coker wrote:
> > On Sun, 29 Aug 2004 02:45, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
wrote:
> > > i'm running kdm 3.3, also i'm running an "immediate user login" with no
> > > password.
> > >
> > > added these to get it to work.
> > >
> > > also as you can see i changed the type of /etc/qt3 to etc_runtime_t.
> >
> > file_type_auto_trans(xdm_t, var_run_t, xdm_var_run_t, { dir fifo_file} )
> >
> > This won't work properly due to a limitation of the file_type_trans()
> > macro.
>
> urrrr... are you sure? have there been recent changes [in last month]
> that _stop_ this from working?
ifelse(`$4', `dir', `
allow $1 $3:$4 create_dir_perms;
', `
ifelse(`$4', `lnk_file', `
allow $1 $3:$4 create_lnk_perms;
', `
allow $1 $3:$4 create_file_perms;
')dnl end ifelse lnk_file
')dnl end if dir
The above is in file_type_trans(). Specifying "dir" with something else means
that create_file_perms will be granted instead of create_dir_perms.
It's been like that ever since I added a fourth parameter to file_type_trans()
and file_type_auto_trans().
> > allow xdm_t init_t:process { signal };
> > #EXE=/sbin/halt : signal
> >
> > allow xdm_t xdm_t:capability { sys_boot };
> >
> > I think that we need a different domain for this.
>
> that'd be nice.
>
> oh - this is what i was referring to about "does anyone _use_ kde"
> because the without xdmctl thing (allowing /var/run/xdmctl/* to be
> xdm_var_run_t etc.) and without the above, you can't run "shutdown"
> from the "logout" menu.
I think that no-one but you uses kdm. Lots of people use KDE including me.
> > can_exec(xdm_t, xsession_exec_t)
> >
> > That looks like a bug. xsession_exec_t scripts are supposed to execute
> > in user context. Looks like the kdm patch does not set the execute
> > context everywhere that it should.
>
> oh. ah.... that patch. um.... the one i haven't applied because i
> downloaded kde 3.3 and i thought i could get away with putting in
> pam_selinux.so into /etc/pam.d/kdm because i didn't want to go through
> _yet another_ kdebase-3.x download and build cycle.
pam_selinux.so never worked properly for xdm type programs.
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2004-08-29 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-28 16:45 patches for xdm.te for kdm 3.3 Luke Kenneth Casson Leighton
2004-08-29 7:21 ` Russell Coker
2004-08-29 9:11 ` Luke Kenneth Casson Leighton
2004-08-29 10:49 ` Russell Coker [this message]
2004-08-29 12:04 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408292049.24183.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=lkcl@lkcl.net \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.