From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 1/2] Add fcontext for sshd pidfile and directory used for privsep
Date: Mon, 27 Jan 2014 13:23:02 -0500 [thread overview]
Message-ID: <52E6A406.3020305@tresys.com> (raw)
In-Reply-To: <1390646637-20687-1-git-send-email-bigon@debian.org>
On 01/25/14 05:43, Laurent Bigonville wrote:
> diff --git a/policy/modules/services/ssh.te b/policy/modules/services/ssh.te
> index 30726f2..a19c9f9 100644
> --- a/policy/modules/services/ssh.te
> +++ b/policy/modules/services/ssh.te
> @@ -34,6 +34,7 @@ ssh_server_template(sshd)
> init_daemon_domain(sshd_t, sshd_exec_t)
>
> ifdef(`distro_debian',`
> + allow sshd_t sshd_var_run_t:dir { getattr search };
> init_daemon_run_dir(sshd_var_run_t, "sshd")
> ')
This looks like it should be in ssh_server_template(). Also please use search_dir_perms permission set.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-01-27 18:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 10:43 [refpolicy] [PATCH 1/2] Add fcontext for sshd pidfile and directory used for privsep Laurent Bigonville
2014-01-25 10:43 ` [refpolicy] [PATCH 2/2] Add fcontext for rsyslog pidfile Laurent Bigonville
2014-01-27 18:24 ` Christopher J. PeBenito
2014-01-27 18:23 ` Christopher J. PeBenito [this message]
2014-01-27 22:18 ` [refpolicy] [PATCH 1/2] Add fcontext for sshd pidfile and directory used for privsep Laurent Bigonville
2014-02-01 3:02 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2014-02-05 21:23 Laurent Bigonville
2014-02-06 11:57 ` Laurent Bigonville
2014-02-06 14:03 ` Christopher J. PeBenito
2014-02-06 14:03 ` Christopher J. PeBenito
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=52E6A406.3020305@tresys.com \
--to=cpebenito@tresys.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.