From: domg472@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [ screen patch 1/1] Add screen-locking functionality. Signed-off-by: Dominick Grift <domg472@gmail.com>
Date: Thu, 22 Oct 2009 15:56:36 +0200 [thread overview]
Message-ID: <20091022135635.GA3562@notebook3.grift.internal> (raw)
In-Reply-To: <1256219581.28212.5.camel@gorn.columbia.tresys.com>
On Thu, Oct 22, 2009 at 09:53:01AM -0400, Christopher J. PeBenito wrote:
> On Thu, 2009-10-22 at 11:14 +0200, Dominick Grift wrote:
> > @@ -146,4 +148,8 @@ template(`screen_role_template',`
> > fs_list_nfs($1_screen_t)
> > fs_read_nfs_symlinks($1_screen_t)
> > ')
> > +
> > + optional_policy(`
> > + dbus_system_bus_client($1_screen_t)
> > + ')
>
> Is this an unrelated change?
No it is related:
allow dgrift_screen_t chkpwd_exec_t:file { read execute open execute_no_trans };
allow dgrift_screen_t self:capability { audit_write dac_override };
allow dgrift_screen_t self:fifo_file { write read ioctl };
allow dgrift_screen_t self:netlink_audit_socket { nlmsg_relay write create read };
allow dgrift_screen_t system_dbusd_t:unix_stream_socket connectto;
allow dgrift_screen_t system_dbusd_var_run_t:sock_file write;
This is all related to screen-locking
>
> --
> Chris PeBenito
> Tresys Technology, LLC
> (410) 290-1411 x150
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20091022/0705dba1/attachment.bin
next prev parent reply other threads:[~2009-10-22 13:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 9:14 [refpolicy] [ screen patch 1/1] Add screen-locking functionality. Signed-off-by: Dominick Grift <domg472@gmail.com> Dominick Grift
2009-10-22 13:53 ` Christopher J. PeBenito
2009-10-22 13:56 ` Dominick Grift [this message]
2009-10-22 14:05 ` Christopher J. PeBenito
2009-10-22 14:13 ` Dominick Grift
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=20091022135635.GA3562@notebook3.grift.internal \
--to=domg472@gmail.com \
--cc=refpolicy@oss.tresys.com \
/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.