SEC 1.4 NO IDEA Avatar
  1. OMG Issue

SEC14 — SECIOP ContextId

  • Key: SEC14-50
  • Legacy Issue Number: 5526
  • Status: open  
  • Source: Adiron, LLC ( Polar Humenn)
  • Summary:

    CORBA Security SECIOP.

    In SECIOP, one RTF changed a field in the SECIOP Message Header

    struct ulonglong

    { unsigned long low; unsigned long high; }


    // This should be changed to unsigned long long
    typedef ulonglong ContextId;


    typedef unsigned long long ContextId;

    because of the introduction of the long long type into CORBA.

    This modification changes the specification the CDR encoding of the
    structure, because what was compact 8 byte sequence aligned on a 4 byte
    boundary. now became an 8 byte sequence aligned on an 8 byte boundary.

    Each SECIOP message is preceded with a GIOP Message header, which is 12
    bytes. Each SECIOP message, which is specified by a struct, starts with
    the ContextId. Strict interpretation of the encoding rules makes the
    SECIOP messages incompatiable, as the space between the header and the
    message must now contain 4 bytes padding.

    Proposed Resolution: revert back to the struct ulonglong definition.

  • Reported: SEC 1.4 — Fri, 19 Jul 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT