25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Login facility Provides the environment for a user to log in <strong>and</strong><br />

initialize the security environment <strong>and</strong> credentials.<br />

These services enable user authentication, secure communication, authorized<br />

access to resources, <strong>and</strong> proper enforcement of security.<br />

The DCE security service communicates with the Cell Directory Service to<br />

advertise its existence to the other systems that are part of the cell. The DCE<br />

security service also uses the Distributed Time Service to obtain time stamps for<br />

use in many of its processes.<br />

13.3.2 Authentication service<br />

The role of the authentication service is to allow principals to positively identify<br />

themselves <strong>and</strong> participate in a DCE network. Both users <strong>and</strong> servers<br />

authenticate themselves in a DCE environment, unlike security in most other<br />

client/server systems, where only users are authenticated. There are two distinct<br />

steps to authentication. At initial logon time, the Kerberos third-party protocol is<br />

used within DCE to verify the identity of a client requesting to participate in a<br />

DSS network. This process results in the client obtaining credentials, which form<br />

the basis for setting up secure sessions with DCE servers when the user tries to<br />

access resources.<br />

In DCE Version 1.1, the idea of preauthentication was introduced, which is not<br />

present in the Kerberos authentication protocols. Preauthentication protects the<br />

security server from a rogue client trying to guess valid user IDs in order to hack<br />

into the system. In DCE 1.1, there are three protocols for preauthentication:<br />

No preauthentication This is provided to support DCE clients earlier than<br />

Version 1.1.<br />

Timestamps This is used by DCE Version 1.1 clients that are<br />

unable to use the third-party protocol. An encrypted<br />

time stamp is sent to the security server. The time<br />

stamp is decrypted, <strong>and</strong> if the time is within five<br />

minutes, the user is considered preauthenticated. This<br />

option needs to be specified for cell administrators <strong>and</strong><br />

non-interactive principals.<br />

Third-party This is the default used by DCE Version 1.1 (<strong>and</strong> later)<br />

clients. It is similar to the time stamps protocol, but<br />

additional information about the client is also<br />

encrypted in various keys.<br />

502 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!