busybox with selinux
Henry Zhang <[email protected]> Tue, 15 Aug 2023 17:29:11 -0700
| Newsgroups | gmane.linux.redhat.fedora.selinux |
|---|---|
| Message-ID | <CANTW0yoCnysgp5PsMMqB4QQwbwAPkMwJScHE8vOgmmj4ruZB7Q@mail.gmail.com> |
--===============7647417744808509319== Content-Type: multipart/alternative; boundary="0000000000001b15430602ff63c6" --0000000000001b15430602ff63c6 Content-Type: text/plain; charset="UTF-8" Hi folks, New version of SELinux complains of busybox when relabeling. My busybox was compiled as CONFIG_FEATURE_INDIVIDUAL=n That means all applets of busybox share the same inode. But SElinux requires each file assigned to an individual inode so that each file can be defined by file_contexts. Any suggestions? Thanks ---henry --0000000000001b15430602ff63c6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi folks,</div><div><br></div><div>New version of SEL= inux complains of busybox when relabeling. <br></div><div>My busybox was co= mpiled as <span><span class=3D"gmail-ui-provider en gmail-bgi gmail-bfl gma= il-bgj gmail-bgk gmail-bgl gmail-bgm gmail-bgn gmail-bgo gmail-bgp gmail-bg= q gmail-bgr gmail-bgs gmail-bgt gmail-bgu gmail-bgv gmail-bgw gmail-bgx gma= il-bgy gmail-bgz gmail-bha gmail-bhb gmail-bhc gmail-bhd gmail-bhe gmail-bh= f gmail-bhg gmail-bhh gmail-bhi gmail-bhj gmail-bhk gmail-bhl gmail-bhm gma= il-bhn gmail-bho" dir=3D"ltr">CONFIG_FEATURE_INDIVIDUAL=3Dn</span></span></= div><div><span><span class=3D"gmail-ui-provider en gmail-bgi gmail-bfl gmai= l-bgj gmail-bgk gmail-bgl gmail-bgm gmail-bgn gmail-bgo gmail-bgp gmail-bgq= gmail-bgr gmail-bgs gmail-bgt gmail-bgu gmail-bgv gmail-bgw gmail-bgx gmai= l-bgy gmail-bgz gmail-bha gmail-bhb gmail-bhc gmail-bhd gmail-bhe gmail-bhf= gmail-bhg gmail-bhh gmail-bhi gmail-bhj gmail-bhk gmail-bhl gmail-bhm gmai= l-bhn gmail-bho" dir=3D"ltr">That means all </span></span>applets of busybo= x share the same inode.</div><div>But SElinux requires each file assigned t= o an individual inode so that each file can be defined by file_contexts.</d= iv><div><br></div><div>Any suggestions?</div><div><br></div><div>Thanks</di= v><div><br></div><div>---henry<br></div><div><br></div></div> --0000000000001b15430602ff63c6-- --===============7647417744808509319== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18Kc2VsaW51eCBt YWlsaW5nIGxpc3QgLS0gc2VsaW51eEBsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpUbyB1bnN1YnNj cmliZSBzZW5kIGFuIGVtYWlsIHRvIHNlbGludXgtbGVhdmVAbGlzdHMuZmVkb3JhcHJvamVjdC5v cmcKRmVkb3JhIENvZGUgb2YgQ29uZHVjdDogaHR0cHM6Ly9kb2NzLmZlZG9yYXByb2plY3Qub3Jn L2VuLVVTL3Byb2plY3QvY29kZS1vZi1jb25kdWN0LwpMaXN0IEd1aWRlbGluZXM6IGh0dHBzOi8v ZmVkb3JhcHJvamVjdC5vcmcvd2lraS9NYWlsaW5nX2xpc3RfZ3VpZGVsaW5lcwpMaXN0IEFyY2hp dmVzOiBodHRwczovL2xpc3RzLmZlZG9yYXByb2plY3Qub3JnL2FyY2hpdmVzL2xpc3Qvc2VsaW51 eEBsaXN0cy5mZWRvcmFwcm9qZWN0Lm9yZwpEbyBub3QgcmVwbHkgdG8gc3BhbSwgcmVwb3J0IGl0 OiBodHRwczovL3BhZ3VyZS5pby9mZWRvcmEtaW5mcmFzdHJ1Y3R1cmUvbmV3X2lzc3VlCg== --===============7647417744808509319==--