Skip to contentSkip to conversation

Is this a module bug?

DISCUSSION Russell Coker 2 participants 2 messages May 22, 2002 – May 24, 2002 1 message not in the archive SELinux security module

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 000501c20190$eec4f9c0$2c1801d0@Dakota

#1 lore raw
Quoted 4 lines · Steve

I'm away at an offsite this week, so I can't look into this closely. However, offhand, anything that is done during module initialization will occur in the context of the process that performed the insertion, so it will show up under kmod_t or insmod_t. Hence, this isn't surprising.

Hmm. So we just have to give insmod_t and kmod_t all capabilities?

Signature · 9 lines
If you send email to me or to a mailing list that I use which has >4 lines
of legalistic junk at the end then you are specifically authorizing me to do
whatever I wish with the message and all other messages from your domain, by
posting the message you agree that your long legalistic sig is void.

--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to [email protected] with
the words "unsubscribe selinux" without quotes as the message.
#2 lore raw
Quoted 1 line · Russell Coker

Hmm. So we just have to give insmod_t and kmod_t all capabilities?

insmod_t and kmod_t will need all permissions necessary to initialize any modules that you plan on inserting, as the initialization code is run in the context of the inserting process.

--
Stephen D. Smalley, NAI Labs
[email protected]

--
You have received this message because you are subscribed to the selinux list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.