From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] The kerberos_keytab_template() template is deprecated: Breaks monolithic built (out-of-scope)
Date: Mon, 23 Sep 2013 14:28:38 -0400 [thread overview]
Message-ID: <52408856.7000904@tresys.com> (raw)
In-Reply-To: <1376650987-16490-1-git-send-email-dominick.grift@gmail.com>
On 08/16/2013 07:03 AM, Dominick Grift wrote:
>
> This keytab functionality should be re-evaluated because it does not
> make sense in its current implementation
>
> Signed-off-by: Dominick Grift <dominick.grift@gmail.com>
> diff --git a/policy/modules/services/ssh.te b/policy/modules/services/ssh.te
> index eada65c..568c335 100644
> --- a/policy/modules/services/ssh.te
> +++ b/policy/modules/services/ssh.te
> @@ -74,6 +74,9 @@
> typealias ssh_home_t alias { auditadm_home_ssh_t secadm_home_ssh_t };
> userdom_user_home_content(ssh_home_t)
>
> +type sshd_keytab_t;
> +files_type(sshd_keytab_t)
> +
> ##############################
> #
> # SSH client local policy
> @@ -224,6 +227,8 @@
> allow sshd_t self:netlink_route_socket r_netlink_socket_perms;
> allow sshd_t self:key { search link write };
>
> +allow sshd_t sshd_keytab_t:file read_file_perms;
> +
> manage_dirs_pattern(sshd_t, sshd_tmp_t, sshd_tmp_t)
> manage_files_pattern(sshd_t, sshd_tmp_t, sshd_tmp_t)
> manage_sock_files_pattern(sshd_t, sshd_tmp_t, sshd_tmp_t)
> @@ -261,7 +266,8 @@
> ')
>
> optional_policy(`
> - kerberos_keytab_template(sshd, sshd_t)
> + kerberos_read_keytab(sshd_t)
> + kerberos_use(sshd_t)
> ')
Merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
prev parent reply other threads:[~2013-09-23 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 11:03 [refpolicy] [PATCH] The kerberos_keytab_template() template is deprecated: Breaks monolithic built (out-of-scope) Dominick Grift
2013-08-21 13:19 ` Christopher J. PeBenito
2013-08-21 13:42 ` Dominick Grift
2013-08-26 13:49 ` Daniel J Walsh
2013-09-23 18:28 ` Christopher J. PeBenito [this message]
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=52408856.7000904@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.