From: Carlos Anisio Monteiro <monteiro@ipen.br>
To: selinux@tycho.nsa.gov
Subject: process context
Date: Thu, 16 Oct 2003 16:57:26 -0200 [thread overview]
Message-ID: <3F8EEA16.8090908@ipen.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 1410 bytes --]
Hi.
The system have many process running in the following context:
system_u:system_r:kernel_t (see example below).
PID CONTEXT COMMAND
1 system_u:system_r:kernel_t init [2]
2 system_u:system_r:kernel_t [ksoftirqd/0]
3 system_u:system_r:kernel_t [events/0]
7 system_u:system_r:kernel_t [kswapd0]
8 system_u:system_r:kernel_t [aio/0]
9 system_u:system_r:kernel_t [kseriod]
33 system_u:system_r:kernel_t [kjournald]
250 system_u:system_r:kernel_t /sbin/syslogd
253 system_u:system_r:kernel_t /sbin/klogd
262 system_u:system_r:kernel_t /usr/sbin/inetd
346 system_u:system_r:kernel_t sendmail: MTA: accepting
connections
373 system_u:system_r:kernel_t /usr/sbin/cron
378 system_u:system_r:kernel_t /sbin/getty 38400 tty2
379 system_u:system_r:kernel_t /sbin/getty 38400 tty3
This is happen in the time of boot.
Is this correct? Any process, p.ex. init, syslogd, klogd, shouldn't they
running in the proper context?
P.ex.:
init - system_u:system_r:init_t
klogd - system_u:system_r:klogd_t
cron - system_u:system_r:cron_t
If yes. How I resolve ???
thanks.
--
Carlos Anisio Monteiro <monteiro@ipen.br>
IPEN/CNEN-SP
Sao Paulo - Brasil
[-- Attachment #2: Type: text/html, Size: 3172 bytes --]
next reply other threads:[~2003-10-16 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 18:57 Carlos Anisio Monteiro [this message]
2003-10-17 3:27 ` process context Russell Coker
2003-10-17 4:17 ` Russell Coker
2003-10-17 10:36 ` kamal
2003-10-17 11:24 ` Russell Coker
2003-10-17 12:08 ` Stephen Smalley
2003-10-17 12:03 ` Stephen Smalley
2003-10-20 10:54 ` Carlos Anisio Monteiro
2003-10-20 14:01 ` Daniel J Walsh
2003-10-21 1:07 ` Russell Coker
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=3F8EEA16.8090908@ipen.br \
--to=monteiro@ipen.br \
--cc=selinux@tycho.nsa.gov \
/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.