Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 00/15] packages: Add SELinux modules to some packages
Date: Mon, 28 Dec 2020 09:31:33 +0100	[thread overview]
Message-ID: <20201228093133.3da428af@bootlin.com> (raw)
In-Reply-To: <160865249576.1448242.9915039771107087372@kwain.local>

Hi Antoine,

Thanks for the review !

On Tue, 22 Dec 2020 16:54:55 +0100
Antoine Tenart <atenart@kernel.org> wrote:

>Hi Maxime,
>
>Quoting Maxime Chevallier (2020-12-22 16:07:21)
>> 
>> Following the recent support for the SELinux refpolicy and the ability
>> for packages to select their own SELinux module in the refpolicy [1],
>> this series adds a first batch of matching between packages and their
>> respective module.  
>
>Nice to see packages using this feature :)
>
>> This series focuses on the tools that are impacted by the following
>> modules in the refpolicy [2] :
>> 
>>   - services/networkmanager, which adds support for :
>>     - dhcp  
>
>I'm not sure about this one. When looking at the module definitions
>dhclient and dhcpcd seem to be supported by system/sysnetwork rather
>than than by services/networkmanager. (Haven't built an image to test
>though).

You're correct, I'll remove that from the list for now. It does seem
that services/networkmanager also references some files in /etc/dhcp,
hence the confusion. 

>>     - iwd
>>     - network-manager
>>     - wpa_supplicant
>> 
>>   - system/ipatbles, which adds support for :
>>     - ebtables
>>     - ipset
>>     - iptables
>>     - nftables
>> 
>>   - admin/netutils, which adds support for :
>>     - fping
>>     - iputils  
>
>iputils can install lots of utilities based on the configuration, many
>of which are supported by admin/netutils. Some are not supported in the
>refpolicy, and some by other modules, such as rdisc or tftpd.
>
>I think the selinux module selection should be conditional depending on
>the utilities installed by the iputils package, to avoid installing an
>unused selinux module and to fix the support of others.

You're right, I'll add the conditionnals :)

>>     - mtr
>>     - nmap
>>     - tcpdump
>> 
>>   - services/entropyd, which adds support for :
>>     - haveged
>>     - jitterentropy-library  
>
>The other selinux module selections LGTM.

Thanks for the thourough review !

Maxime

>> With this series, the above-mentionned tools can now be used on systems
>> that have SELinux enabled.
>> 
>> This series was split per-package, which generates lots of one-liner
>> patches. Due to the nature of the changes, I expect more patches like
>> that to follow, so we might also use a "one package per module" approach
>> if you want.  
>
>> Maxime Chevallier (15):
>>   packages/dhcp: add SELinux module  
>
>Nitpick: s/packages/package/
>
>>   package/iwd: add SELinux module
>>   package/network-manager: add SELinux module
>>   package/wpa_supplicant: add SELinux module
>>   package/ebtables: add SELinux module
>>   package/ipset: add SELinux module
>>   package/iptables: add SELinux module
>>   package/nftables: add SELinux module
>>   package/fping: add SELinux module
>>   package/iputils: add SELinux module
>>   package/mtr: add SELinux module
>>   package/nmap: add SELinux module
>>   package/tcpdump: add SELinux module
>>   package/haveged: add SELinux module
>>   package/jitterentropy-library: add SELinux module  
>
>Thanks!
>Antoine



-- 
Maxime Chevallier, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

      reply	other threads:[~2020-12-28  8:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 15:07 [Buildroot] [PATCH 00/15] packages: Add SELinux modules to some packages Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 01/15] packages/dhcp: add SELinux module Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 02/15] package/iwd: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 03/15] package/network-manager: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 04/15] package/wpa_supplicant: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 05/15] package/ebtables: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 06/15] package/ipset: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 07/15] package/iptables: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 08/15] package/nftables: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 09/15] package/fping: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 10/15] package/iputils: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 11/15] package/mtr: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 12/15] package/nmap: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 13/15] package/tcpdump: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 14/15] package/haveged: " Maxime Chevallier
2020-12-22 15:07 ` [Buildroot] [PATCH 15/15] package/jitterentropy-library: " Maxime Chevallier
2020-12-22 15:54 ` [Buildroot] [PATCH 00/15] packages: Add SELinux modules to some packages Antoine Tenart
2020-12-28  8:31   ` Maxime Chevallier [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=20201228093133.3da428af@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox