All of lore.kernel.org
 help / color / mirror / Atom feed
From: pebenito@ieee.org (Chris PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] bootloader: add permissions to read boot files in order to generate a configuration file
Date: Sat, 11 Feb 2017 14:51:54 -0500	[thread overview]
Message-ID: <d1a5de89-c6ca-c23d-a4d8-8c28f2665d69@ieee.org> (raw)
In-Reply-To: <20170208021335.GA2470@meriadoc.perfinion.com>

On 02/07/17 21:13, Jason Zaman via refpolicy wrote:
> On Wed, Feb 08, 2017 at 12:32:32AM +0100, Guido Trentalancia via refpolicy wrote:
>> Allow the bootloader to read boot files in order to generate
>> a configuration file.
>>
>> Signed-off-by: Guido Trentalancia <guido@trentalancia.net>
>
> NACK. this wont work. Just use the patch I posted
> http://oss.tresys.com/pipermail/refpolicy/2017-February/009011.html
> [PATCH v2] bootloader: grub needs to manage grub.cfg and read kernels

I've decided to revert this patch.  A nonfunctional system app like this 
is not acceptable.  I am still open to a change along these lines, 
though arguably because bootloader has raw disk access, it doesn't 
matter much if it can overwrite the kernel via normal file access.


>> ---
>>  policy/modules/admin/bootloader.te |    1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff -pru refpolicy-git-08022017-orig/policy/modules/admin/bootloader.te refpolicy-git-08022017/policy/modules/admin/bootloader.te
>> --- refpolicy-git-08022017-orig/policy/modules/admin/bootloader.te	2016-12-29 22:48:16.446818415 +0100
>> +++ refpolicy-git-08022017/policy/modules/admin/bootloader.te	2017-02-08 00:14:22.923674773 +0100
>> @@ -108,6 +108,7 @@ corecmd_exec_all_executables(bootloader_
>>  domain_use_interactive_fds(bootloader_t)
>>
>>  files_create_boot_dirs(bootloader_t)
>> +files_read_boot_files(bootloader_t)
>>  files_read_etc_files(bootloader_t)
>>  files_read_usr_src_files(bootloader_t)
>>  files_read_usr_files(bootloader_t)
>> _______________________________________________
>> refpolicy mailing list
>> refpolicy at oss.tresys.com
>> http://oss.tresys.com/mailman/listinfo/refpolicy
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
>


-- 
Chris PeBenito

  reply	other threads:[~2017-02-11 19:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-23  0:22 [refpolicy] [PATCH] bootloader: stricter permissions and more tailored file contexts Guido Trentalancia
2016-12-27 15:53 ` Chris PeBenito
2017-02-05  5:44 ` Jason Zaman
2017-02-07 23:12   ` Guido Trentalancia
2017-02-07 23:26     ` Chris PeBenito
2017-02-07 23:32       ` [refpolicy] [PATCH] bootloader: add permissions to read boot files in order to generate a configuration file Guido Trentalancia
2017-02-08  2:13         ` Jason Zaman
2017-02-11 19:51           ` Chris PeBenito [this message]
2017-02-11 20:18             ` Guido Trentalancia
2017-02-11 20:23               ` Dominick Grift
2017-02-11 20:31                 ` Dominick Grift
2017-02-11 20:47                   ` Dominick Grift
2017-02-11 20:51                     ` Guido Trentalancia
2017-02-07 23:39       ` [refpolicy] [PATCH] bootloader: stricter permissions and more tailored file contexts Guido Trentalancia
2017-02-08  2:17         ` Jason Zaman
2017-02-08  5:45           ` Guido Trentalancia

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=d1a5de89-c6ca-c23d-a4d8-8c28f2665d69@ieee.org \
    --to=pebenito@ieee.org \
    --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.