SELinux-Refpolicy Archive mirror
 help / color / mirror / Atom feed

From: Ashish Mishra <ashishm@mvista.com>
To: selinux-refpolicy@vger.kernel.org,
	Paul Moore <paul@paul-moore.com>,
	SElinux list <selinux@vger.kernel.org>
Subject: How is policy.31 created from modules under /usr/share/selinux
Date: Sun, 6 Dec 2020 00:49:14 +0530	[thread overview]
Message-ID: <CAP2OjcjCFYiyMfqa=X__X6g0U0143U5Fd-xGaKJgGNabFUpr7w@mail.gmail.com> (raw)

Hi All  ,

Good Morning .

I am following the SELINUX NOTEBOOK & trying the same at my end .

- The refpolicy modules are copied at /usr/share/selinux/refpolicy
   i can see around 400+ modules there .
   But can senior member' s please help me understand how is the
   /etc/selinux/refpolicy/policy/policy.31  created using the modules
available at
   /usr/share/selinux
   The command i followed :
                $ make install-src
                $ make conf
                $ make load ( tried even $ make install )
                $ make install-headers


- This can help me to debug an issue where i am trying to get selinux
of my custom
   distro where all the make command are successfully executed but the policy.31
   is not getting created

- I can even see the "include" folder also getting created for make
install-headers

Any pointers will be helpful or please let me know if i am missing any
aspect here .

Thanks ,
Ashish.

next             reply	other threads:[~2020-12-05 19:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-05 19:19 Ashish Mishra [this message]
2020-12-06 15:29 ` How is policy.31 created from modules under /usr/share/selinux Richard Haines
2020-12-06 16:30   ` Ashish Mishra
2020-12-06 17:15     ` Richard Haines
2020-12-07  1:21       ` Ashish Mishra
2020-12-07 12:39         ` Richard Haines
2020-12-07 13:26           ` Ashish Mishra
2020-12-08 15:36             ` Chris PeBenito
2020-12-08 15:58               ` Ashish Mishra
2020-12-09  9:53                 ` Richard Haines
2020-12-09 14:12                   ` Ashish Mishra
2020-12-09 14:37                     ` Richard Haines
2020-12-09 15:07                       ` Steve Lawrence
2020-12-09 16:13                         ` Richard Haines
2020-12-09 22:02                           ` Chris PeBenito
2020-12-13 17:06                             ` Ashish Mishra
2020-12-14 15:16                               ` Chris 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='CAP2OjcjCFYiyMfqa=X__X6g0U0143U5Fd-xGaKJgGNabFUpr7w@mail.gmail.com' \
    --to=ashishm@mvista.com \
    --cc=paul@paul-moore.com \
    --cc=selinux-refpolicy@vger.kernel.org \
    --cc=selinux@vger.kernel.org \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).