Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP CIFS Client A.01.09 Administrator's Guide: HP-UX 11.0 and 11i version 1 and 2 > Chapter 3 CIFS Security and Authentication

Introduction

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

One of the important characteristics of the CIFS file-sharing protocol is its security model. Before a user on a CIFS client can access the mountpoint of a CIFS server, the user must be authenticated by the server (the user must login to the server). Four login methods are available, they are explained in the following pages. Restrictions at the file or directory level on the server’s filesystem are also enforced by the server.

In contrast, NFS relies solely upon file and directory level permissions on the server’s filesystem, in conjunction with the user’s UNIX uid.

Authentication Protocols

The CIFS Client supports two authentication protocols. These protocols are configured on a global or server specific basis in the CIFS Client configuration file (/etc/opt/cifsclient/cifscient.cfg) by the system administrator:

  • Windows NT LanManager (NTLM) NTLM is a challenge-response strategy protocol. The server sends a challenge key to the client which the client returns to the server encrypted with the user’s password. The server decrypts the key and authenticates the user. No semblance of the user’s password is transmitted over the network.

  • Kerberos Kerberos is a distributed authentication service that allows a client running on behalf of a user to prove its identity to an application server without sending data across the network that might allow an attacker to subsequently impersonate the user. Kerberos is a secure, industry standard authentication protocol. It provides significant improvements over the NTLM protocol.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.