All of lore.kernel.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	"SELinux-ML(NSA)" <selinux@tycho.nsa.gov>,
	James Morris <jmorris@redhat.com>
Subject: Re: [POLICY/PATCH] IA-64 Boot Partition
Date: Tue, 19 Apr 2005 01:54:25 +0900	[thread overview]
Message-ID: <4263E641.9010100@kaigai.gr.jp> (raw)
In-Reply-To: <1113827271.28051.39.camel@moss-spartans.epoch.ncsc.mil>

Hi,

>>BTW, what archtectures are used and checked by SELinux's people ?
>>For example, kernel panic is occured on the 2.6.6 or former kernel for IA-64
>>when SELinux is enabled. This phenomenon have been overlooked.
>>
>>I can validate the evidence on IA64/i386 environment.
>>Is there a person who can try to run SELinux on infrequent(not i386) plathome?
>
>
> All of my machines are x86, so I'm afraid I can't be of much help there.

In Japan, Secure-OS such as SELinux is hoped for embedded computing field,
because applying the latest security patch for those application is not
as easy as one for our desktop PC.
So, I wonder who did evaluate the behavior on ARM/MIPS archtecture.

# This is NOT NEC's bussiness requirement, my personal interresting. :-)

Thanks,
-- 
DO NOTHING IS THE WORST POLICY.
KaiGai Kohei <kaigai@kaigai.gr.jp>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-04-18 16:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-16  6:57 [POLICY/PATCH] IA-64 Boot Partition KaiGai Kohei
2005-04-16 15:55 ` Christopher J. PeBenito
2005-04-16 16:25   ` KaiGai Kohei
2005-04-16 17:28     ` Christopher J. PeBenito
2005-04-18 12:27     ` Stephen Smalley
2005-04-18 16:54       ` KaiGai Kohei [this message]
2005-04-18 17:14         ` Stephen Smalley
2005-04-19  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=4263E641.9010100@kaigai.gr.jp \
    --to=kaigai@kaigai.gr.jp \
    --cc=cpebenito@tresys.com \
    --cc=jmorris@redhat.com \
    --cc=sds@tycho.nsa.gov \
    --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.