Description
The endpoint object operates on RPC endpoint mappings on the local host. Endpoints contain an interface identifier and one or more string bindings; optionally they contain object UUIDs and an annotation.
Endpoint mappings are stored in the endpoint map maintained by the DCE daemon (dced) for DCE version 1.1 hosts. DCE Version 1.0 uses the RPC daemon (rpcd) to maintain the endpoint map. The server object has some operations (for example, disable and enable) that affect endpoints maintained by the dced. However, server object operations do not operate on endpoints maintained by DCE Version 1.0 hosts. The endpoint object affects all endpoint maps, whether maintained by rpcd or dced.
Because endpoints have no names, the argument to these commands is not the name of an endpoint. Earlier versions of rpccp and rpcd allowed remote access to endpoints, but this was a security problem. Only the endpoint show operation allows access to endpoint maps on remote systems. The server object allows some remote operations on dced endpoint maps which are free of the security problem, depending on how dced is configured.
Use the various endpoint subcommands to create, delete, and show RPC endpoint information in local host endpoint maps.