Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Method for Auditing all Distributed Computing Environment Core Daemons Remotely

IP.com Disclosure Number: IPCOM000118766D
Original Publication Date: 1997-Jun-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 102K

Publishing Venue

IBM

Related People

Tran, TM: AUTHOR

Abstract

Disclosed is a method for auditing all the Distributed Computing Environment (DCE) core Daemons remotely. The core Daemons include: DCED, SECD (master and replica), CDSD (master and replica), CDSADV, DTSD, and GDAD.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 50% of the total text.

Method for Auditing all Distributed Computing Environment Core Daemons
Remotely

      Disclosed is a method for auditing all the Distributed
Computing Environment (DCE) core Daemons remotely.  The core Daemons
include:  DCED, SECD (master and replica), CDSD (master and replica),
CDSADV, DTSD, and GDAD.

      The method consists of three steps.  The first step is to bind
to the core Daemons remotely.  The second step is to send the Audit
Event Records to the main Audit Trail.  The last step is to list all
possible actions that DCE Users could take after the Daemon was
killed abnormally.

      To achieve the first step, it is necessary to create two files
during configuration time for each Monitored Daemon.  The first file
is called daemon_identity, and it contains the Host name where the
Daemon is going to reside.  The second file is called daemon_binding
and it contains the String Bindings of the Daemon.  The examples of
these two files are shown below:
       o The daemon_identity file:
           hosts/dceos2.austin.ibm.com/self
       o The daemon_binding file:
           ncacn_ip_tcp:129.35.69.22(1117)
           ncacn_ip_udp:129.35.69.22(1122)

      These two files will be placed in /opt/dcelocal/var/<component>
sub-directory of the machine where the Monitoring Tool periodically
runs.  The Monitoring Tool should run on the same system with DCED.
For example:

                            (Image Omitted)

The purposes of creating these two files are:
  1.  To allow the Monitoring Tool to bind to the Monitored
       Daemons remotely for auditing.
  2.  To permit the Monitored Daemons to send the Audit Records
       to the main central Audit Trail file, which is controlled
       by Audit Daemon, before they were killed.

      Recall, the Monitoring Tool is an Application Program which
periodically listens to the Monitored Daemons via a RPC call.  It can
be easily implemented by the means of SMP and EMS.  In the scope of
this paper, it will not be discussed in detail (Refer to SMP and EMS
functions for more details on how to implement the Monitoring Tool).

The bind_to_daemon() routine, which is used in the first step, is
shown as followed:
  void bind_to_daemon(daemon_binding, daemon_identity,
   binding_handle, st);
    fh = fopen(daemon_binding, "r");
    check the file handle, fh
    fget(buff, 1024, fh);
    if (buff(strlen(buff) -1) = '\n')
        buff(strlen(buff) -1) = '\0')
    rpc_string_binding_parse(buff, &obj, &pseq, &addr,
     &endpt, &opt, st);
    check st
    if (pseq = NULL || *pseq = 0)
      rseq = "ip";
    else
      rseq = pseq;
    if (endpt = NULL || *endpt = 0)
      rend = "";
    else
      rend = endpt;
    rpc_string_binding_compose(obj, rseq, addr, rend, opt,
     &binding, st);
    check st
    rpc_string_fro...