Re: [cicm] Key Identifers

"Fitton, John" <jfitton@harris.com> Fri, 03 June 2011 22:29 UTC

Return-Path: <jfitton@harris.com>
X-Original-To: cicm@ietfa.amsl.com
Delivered-To: cicm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 741D8E07F5 for <cicm@ietfa.amsl.com>; Fri, 3 Jun 2011 15:29:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKJHeRDhW0HZ for <cicm@ietfa.amsl.com>; Fri, 3 Jun 2011 15:29:32 -0700 (PDT)
Received: from mlbe2k2.cs.myharris.net (mlbe2k2.cs.myharris.net [137.237.90.89]) by ietfa.amsl.com (Postfix) with ESMTP id C152EE07F2 for <cicm@ietf.org>; Fri, 3 Jun 2011 15:29:32 -0700 (PDT)
Received: from mail pickup service by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC; Fri, 3 Jun 2011 18:29:31 -0400
Received: from mlbe2kpf1.cs.myharris.net ([137.237.89.95]) by mlbe2k2.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 3 Jun 2011 18:29:30 -0400
Received: from MLBMXHTUS1.cs.myharris.net ([137.237.89.77]) by mlbe2kpf1.cs.myharris.net with Microsoft SMTPSVC(6.0.3790.4675); Fri, 3 Jun 2011 18:29:30 -0400
Received: from ROCMXCAHT22.cs.myharris.net (10.64.228.25) by MLBMXHTUS1.cs.myharris.net (137.237.89.77) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 3 Jun 2011 18:29:30 -0400
Received: from ROCMXUS21.cs.myharris.net ([fe80::1161:8dee:2d75:5ac]) by ROCMXCAHT22.cs.myharris.net ([::1]) with mapi id 14.01.0270.001; Fri, 3 Jun 2011 18:29:29 -0400
From: "Fitton, John" <jfitton@harris.com>
To: CICM Discussion List <cicm@ietf.org>
Thread-Topic: [cicm] Key Identifers
Thread-Index: AQHMIiC4MPsFX1Dzn0qnSMClDalVL5SsNdIj
Date: Fri, 03 Jun 2011 22:29:29 +0000
Message-ID: <06D46EAFF7D0C946BEC108DB7CCDC9A608B49452@ROCMXUS21.cs.myharris.net>
References: <E3337014FCBC034BBD725917528D5D7BD08CBF@vcaexch06.hq.corp.viasat.com>
In-Reply-To: <E3337014FCBC034BBD725917528D5D7BD08CBF@vcaexch06.hq.corp.viasat.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.228.55]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 03 Jun 2011 22:29:30.0617 (UTC) FILETIME=[B4A82690:01CC223D]
Subject: Re: [cicm] Key Identifers
X-BeenThere: cicm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: CICM Discussion List <cicm@ietf.org>
List-Id: CICM Discussion List <cicm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cicm>, <mailto:cicm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/cicm>
List-Post: <mailto:cicm@ietf.org>
List-Help: <mailto:cicm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cicm>, <mailto:cicm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2011 22:29:33 -0000

I would imagine that one method would be for the entity desiring to obtain key identifiers would be to list the attributes of the keys that it is interested in. By passing in such an attribute list, then a compilation of the key identifiers which satisfy the attribute list could be provided. Proper Least Privilege restrictions would restrict the entity from including any attributes in the request that are not consistent with the applications needs. These "needs" could be listed in a security policy which is enforced by the Security Model. In that way the application could only find out about keys which a constrained to that attribute set.

________________________________
From: Nanjundiah, Girish [Girish.Nanjundiah@viasat.com]
Sent: Thursday, June 02, 2011 7:17 PM
To: CICM Discussion List
Subject: [cicm] Key Identifers

Hello Everyone,

Sorry if this question is extremely obvious or just hasn’t been answered but I’m a little confused as to how we are meant to access the CICM::CharString identifier attribute of the CICM::Key class. I’m assuming attributes are all private or protected, so how is one to access the identifier? While it is easy to obtain its value with CICM::Key::export, I can’t seem to find a way to set it without adding another function or a constructor for the CICM::Key class…

Thanks,
-Girish Nanjundiah