Issue 2201:  Interfaces are specified using wrong datatype in CORBASEC (sec-rev)
Source:  (, )
Nature:  Uncategorized Issue
Severity: 
Summary: Summary: The CORBASecurity spec. uses three different datatypes for interfaces:
 
  InterfaceDef
  RepositoryID
  Identifier
 
 InterfaceDef should definitely NOT be used, as it can"t be resolved without
 reference to the
 Interface Repository, which would be a big performance penalty for cases where
 the interface"s
 name is simply being matched or used as a lookup key in a local table.
 
 Identifier is also the wrong type; it"s a generic string type and hence not
 type-safe with respect
 to interface names.
 

Resolution: 
Revised Text: 
Actions taken:
November 10, 1998: received issue
November 13, 1998: closed issue
Discussion: 

End of Annotations:=====
Return-Path: <blakley@us.ibm.com>
From: Bob Blakley <blakley@us.ibm.com>
To: <sec-rev@omg.org>, <issues@omg.org>
Subject: Interfaces are specified using wrong datatype in CORBASEC
Date: Tue, 10 Nov 1998 02:45:25 -0500

Juergen, Sec-Revvers:

Issue:

The CORBASecurity spec. uses three different datatypes for interfaces:

 InterfaceDef
 RepositoryID
 Identifier

InterfaceDef should definitely NOT be used, as it can't be resolved
without
reference to the
Interface Repository, which would be a big performance penalty for
cases where
the interface's
name is simply being matched or used as a lookup key in a local table.

Identifier is also the wrong type; it's a generic string type and
hence not
type-safe with respect
to interface names.

Proposed resolution:

Change all typedefs in the CORBASecurity spec. (Chapter 15) which
define
formal parameters through which interface names are passed to have the
type
RepositoryID.

--bob

Bob Blakley
IBM Lead Security Architect
Voice: +1 (512) 838-8133
Fax:    +1 (512) 838-0156
Post:    11400 Burnet Road, Mail Stop 9134, Austin, TX 78758 USA
Internet: blakley@us.ibm.com