All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Santosh Chokhani <SChokhani@cygnacom.com>
Cc: saag@ietf.org, labeled-nfs@linux-nfs.org,
	nfs-discuss@opensolaris.org, nfsv4@ietf.org,
	selinux@tycho.nsa.gov
Subject: Re: [saag] Common labeled security (comment on CALIPSO,	labeled NFSv4)
Date: Fri, 3 Apr 2009 10:42:54 -0500	[thread overview]
Message-ID: <20090403154253.GZ1500@Sun.COM> (raw)
In-Reply-To: <FAD1CF17F2A45B43ADE04E140BA83D48A9FF82@scygexch1.cygnacom.com>

On Fri, Apr 03, 2009 at 11:22:38AM -0400, Santosh Chokhani wrote:
> As part of MISSI and DMS, in mid to late 90's we did work on something
> called Security Policy Information File (SPIF).

Oh, very nice!  Thanks for the pointer.  That would be ISO15816.  I've
found the spec, though it's non-free (hadn't they learned the lesson
with ASN.1??  will they ever learn it??).

> At high level SPIF entailed the following:
> 
> 1.  It was ASN.1 based.

Not surprisingly :)  Converting that to XML is probably the correct
first step in order to ensure adoption, sadly.  (Actually, apparently
that has already been done once, though outside the ISO/ITU-T.)

> 2.  It permitted you to convert the machine representation to human
> readable representation.
> 3.  It permitted you to convert the human readable input to machine
> representation.
> 4.  It mapped labels (hierarchical sensitivity levels and
> non-hierarchical categories) from one labeling policy to another (i.e.,
> establish equivalency mapping)
> 5.  It allowed you to constrain labels since for some policies,
> existence of a category may mean some categories, levels, may be
> included and/or excluded.
> 
> Different labeling policies were indicated by different policy OID.
> 
> Some of the concept from that work may be applicable here. 

I think so!  Except for the part about this spec being non-free.  I
think that means: start over in the IETF.

Nico
-- 

--
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.

  parent reply	other threads:[~2009-04-03 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 15:44 Common labeled security (comment on CALIPSO, labeled NFSv4) Nicolas Williams
     [not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FF82@scygexch1.cygnacom.com>
2009-04-03 15:42   ` Nicolas Williams [this message]
     [not found]     ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FF9E@scygexch1.cygnacom.com>
2009-04-03 17:36       ` [saag] " Nicolas Williams
     [not found]         ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFAF@scygexch1.cygnacom.com>
2009-04-03 19:18           ` Nicolas Williams
     [not found]             ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFBE@scygexch1.cygnacom.com>
2009-04-03 19:57               ` Nicolas Williams
     [not found]                 ` <49D80922.9050700@ieca.com>
2009-04-06 15:11                   ` Nicolas Williams
     [not found]   ` <20090403164522.DEA9A9A4739@odin.smetech.net>
2009-04-03 16:51     ` Nicolas Williams
     [not found]     ` <9C2457A4-328A-4A68-A9D2-6E4B5544078D@Isode.com>
     [not found]       ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFE0@scygexch1.cygnacom.com>
     [not found]         ` <B8FB99E8-17AA-4D4B-A309-8AF79838A304@Isode.com>
     [not found]           ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FFE9@scygexch1.cygnacom.com>
2009-04-06 15:16             ` Nicolas Williams
     [not found]               ` <FAD1CF17F2A45B43ADE04E140BA83D48AA0032@scygexch1.cygnacom.com>
2009-04-06 16:22                 ` Nicolas Williams

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=20090403154253.GZ1500@Sun.COM \
    --to=nicolas.williams@sun.com \
    --cc=SChokhani@cygnacom.com \
    --cc=labeled-nfs@linux-nfs.org \
    --cc=nfs-discuss@opensolaris.org \
    --cc=nfsv4@ietf.org \
    --cc=saag@ietf.org \
    --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.