This directory contains four examples from "DCE Security Programming,"
by Wei Hu, published by O'Reilly & Associates, Inc.

Each of the examples appears in a separate appendix in the book, and
in a compressed tar .Z file in this directory.  Each .Z file contains
all the source code required for building its example, including:

* The .idl interface definition.

* Other .c and .h source files.

* A Makefile, which you will probably have to change before using.
  Libraries and compiler options vary from one system to another.

When you run a tar command to extract files, it creates a subdirectory that
holds all the files pertaining to the example.

The files and corresponding examples are:

unauth.jun95.tar.Z           DCE application without security, Appendix A.

                             A baseline to help you see what a bare-bones
                             RPC application is like without security.  The
                             next three examples add progressively more
                             sophisticated security to this one.

name_based.jun95.tar.Z       Beginning security (not very strong), Appendix B.

                             An illustration of how to incorporate security
                             into a DCE program, although a version that
                             can be compromised.  The server and client
                             authenticate on the basis of principal names.
                             Authorization rules are hard-coded into the
                             server.

pac_based.jun95.tar.Z        Robust security, Appendix C.

                             The example in Appendix B is strengthened here
                             to provide trustworthy security.  Now the PAC
                             is used instead of a name, because PACs are
                             almost impossible to obtain fraudulently.
                             Authorization is still applied rigidly,
                             though.

acl_based.jun95.tar.Z        ACL manager, Appendix D.

                             The final version of the secure application.
                             Now an administrator can add, remove, and
                             change user and group permissions dynamically
                             through the use of ACLs.