From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Sean Turner <turners@ieca.com>
Cc: Santosh Chokhani <SChokhani@cygnacom.com>,
labeled-nfs@linux-nfs.org, selinux@tycho.nsa.gov, saag@ietf.org,
nfs-discuss@opensolaris.org, nfsv4@ietf.org
Subject: Re: [saag] Common labeled security (comment on CALIPSO, labeled NFSv4)
Date: Mon, 6 Apr 2009 10:11:01 -0500 [thread overview]
Message-ID: <20090406151100.GP1500@Sun.COM> (raw)
In-Reply-To: <49D80922.9050700@ieca.com>
On Sat, Apr 04, 2009 at 09:28:02PM -0400, Sean Turner wrote:
> I usually try to find the corresponding ITU spec because I think ITU
> gives out all of it's ASN.1 modules freely? Anyway, here's a link to
> the ITU-T X.841 Spec:
> http://www.itu.int/ITU-T/asn1/database/itu-t/x/x841/2000/index.html
Thanks. I'm sure the spec needs to be read too, not just the ASN.1
module (it's mostly self-evident, but some types, like
LabelAndCertValue, require an explanation).
> The one thing that's missing from the module is definitions for security
> categories. Some suggested categories were defined in Annex B, but it's
> an informative annex so there's no ASN.1 freely available (they wouldn't
> allow them in the normative text/module). Those categories are based on
> FIPS 188 (the syntax is not the same).
>
> Note that some of the syntax for labels has made it's way to some
> IDs/RFCs notably RFC 2634.
Thanks. That's very useful.
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.
next prev parent reply other threads:[~2009-04-06 16:35 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 ` [saag] " Nicolas Williams
[not found] ` <FAD1CF17F2A45B43ADE04E140BA83D48A9FF9E@scygexch1.cygnacom.com>
2009-04-03 17:36 ` 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 [this message]
[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=20090406151100.GP1500@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 \
--cc=turners@ieca.com \
/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.