From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 2/7] New sudo manages timestamp directory in /var/run/sudo
Date: Sun, 23 Nov 2014 13:50:20 +0100 [thread overview]
Message-ID: <20141123125019.GA11067@e145.network2> (raw)
In-Reply-To: <CAPzO=Nwmg66jmx=Pxy1_QP3XH2jSOyuF4MNL0WmMLKJDCRiFog@mail.gmail.com>
On Sat, Nov 22, 2014 at 10:19:47PM +0100, Sven Vermeulen wrote:
> Good catch, I checked against the wrong repo :-( Thanks.
>
> I've resent it with the interface added (although I got the mails
> twice now, my git send-email-fu is not at its peak right now).
>
> Wkr,
> Sven Vermeulen
>
> 2014-11-22 20:55 GMT+01:00 Nicolas Iooss <nicolas.iooss@m4x.org>:
> > 2014-11-22 19:54 GMT+01:00 Sven Vermeulen:
> >> [...]
> >> --- a/policy/modules/admin/sudo.if
> >> +++ b/policy/modules/admin/sudo.if
> >> @@ -52,7 +52,7 @@ template(`sudo_role_template',`
> >> #
> >>
> >> # Use capabilities.
> >> - allow $1_sudo_t self:capability { fowner setuid setgid dac_override sys_nice sys_resource };
> >> + allow $1_sudo_t self:capability { chown fowner setuid setgid dac_override sys_nice sys_resource };
> >> allow $1_sudo_t self:process ~{ ptrace setcurrent setexec setfscreate setrlimit execmem execstack execheap };
> >> allow $1_sudo_t self:process { setexec setrlimit };
> >> allow $1_sudo_t self:fd use;
> >> @@ -117,6 +117,7 @@ template(`sudo_role_template',`
> >> auth_run_chk_passwd($1_sudo_t, $2)
> >> # sudo stores a token in the pam_pid directory
> >> auth_manage_pam_pid($1_sudo_t)
> >> + auth_pid_filetrans_pam_var_run($1_sudo_t, dir, "sudo")
> >
> > This interface does not exist in refpolicy and the build fails because
> > of this. Gentoo policy defines it in authlogin.if and the definition
> > looks good to me:
> > https://github.com/sjvermeu/hardened-refpolicy/blob/9d229675d7084facc9592f1ddab5f976337524f4/policy/modules/system/authlogin.if#L1811
> >
I do not see how /var/run/sudo is associated with pam
--
Dominick Grift
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20141123/b28f95b3/attachment.bin
next prev parent reply other threads:[~2014-11-23 12:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-22 18:54 [refpolicy] [PATCH 0/7] Some simple core policy updates Sven Vermeulen
2014-11-22 18:54 ` [refpolicy] [PATCH 1/7] Run grub(2)-mkconfig in bootloader domain Sven Vermeulen
2014-11-22 18:54 ` [refpolicy] [PATCH 2/7] New sudo manages timestamp directory in /var/run/sudo Sven Vermeulen
2014-11-22 19:55 ` Nicolas Iooss
2014-11-22 21:19 ` Sven Vermeulen
2014-11-23 12:50 ` Dominick Grift [this message]
2014-11-23 14:09 ` Sven Vermeulen
2014-11-23 14:40 ` Dominick Grift
2014-12-02 15:27 ` Christopher J. PeBenito
2014-11-22 18:54 ` [refpolicy] [PATCH 3/7] xfce4-notifyd is an executable Sven Vermeulen
2014-11-22 18:54 ` [refpolicy] [PATCH 4/7] Mark f2fs as a SELinux capable file system Sven Vermeulen
2014-11-22 18:54 ` [refpolicy] [PATCH 5/7] Add in LightDM contexts Sven Vermeulen
2014-11-22 18:54 ` [refpolicy] [PATCH 6/7] Add gfisk and efibootmgr as fsadm_exec_t Sven Vermeulen
2014-11-22 18:54 ` [refpolicy] [PATCH 7/7] Add /var/lib/racoon as runtime directory for ipsec Sven Vermeulen
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=20141123125019.GA11067@e145.network2 \
--to=dac.override@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.