1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
5 <!-- Stuff for xincludes -->
6 <!ENTITY % xinclude SYSTEM "../entities/xinclude.dtd">
9 <!-- entities files to use -->
10 <!ENTITY % global_entities SYSTEM '../entities/global.entities'>
16 <title>Glossary</title>
19 <glossterm>Access Control List</glossterm>
20 <acronym>ACL</acronym>
22 A detailed list of permissions granted to users or groups with respect to file and network
28 <glossterm>Active Directory Service</glossterm>
29 <acronym>ADS</acronym>
31 A service unique to Microsoft Windows 200x servers that provides a centrally managed
32 directory for management of user identities and computer objects, as well as the
33 permissions each user or computer may be granted to access distributed network resources.
34 ADS uses Kerberos-based authentication and LDAP over Kerberos for directory access.
39 <glossterm>Common Internet File System</glossterm>
40 <acronym>CIFS</acronym>
42 The new name for SMB. Microsoft renamed the SMB protocol to CIFS during
43 the Internet hype in the 1990s. At about the time that the SMB protocol was renamed
44 to CIFS, an additional dialect of the SMB protocol was in development. The need for the
45 deployment of the NetBIOS layer was also removed, thus paving the way for use of the SMB
46 protocol natively over TCP/IP (known as NetBIOS-less SMB or <quote>naked</quote> TCP
52 <glossterm>Common UNIX Printing System</glossterm>
53 <acronym>CUPS</acronym>
55 A recent implementation of a high-capability printing system for UNIX developed by
56 <ulink url="http://www.easysw.com/">Easy Software Inc.</ulink> The design objective
57 of CUPS was to provide a rich print processing system that has built-in intelligence
58 that is capable of correctly rendering (processing) a file that is submitted for
59 printing even if it was formatted for an entirely different printer.
65 <glossterm>Domain Master Browser</glossterm>
66 <acronym>DMB</acronym>
68 The Domain Master Browser maintains a list of all the servers that
69 have announced their services within a given workgroup or NT domain.
74 <glossterm>Domain Name Service</glossterm>
75 <acronym>DNS</acronym>
77 A protocol by which computer hostnames may be resolved to the matching IP address/es.
78 DNS is implemented by the Berkeley Internet Name Daemon. There exists a recent version
79 of DNS that allows dynamic name registration by network clients or by a DHCP server.
80 This recent protocol is known as Dynamic DNS (DDNS).
85 <glossterm>Dynamic Host Configuration Protocol</glossterm>
86 <acronym>DHCP</acronym>
88 A protocol that was based on the BOOTP protocol that may be used to dynamically assign
89 an IP address, from a reserved pool of addresses, to a network client or device.
90 Additionally, DHCP may assign all network configuration settings and may be used to
91 register a computer name and its address with a Dynamic DNS server.
96 <glossterm>Ethereal</glossterm>
97 <acronym>ethereal</acronym>
99 A network analyzer, also known as: a network sniffer or a protocol analyzer. Ethereal is
100 freely available for UNIX/Linux and Microsoft Windows systems from
101 <ulink url="http://www.ethereal.com">the Ethereal Web site.</ulink>
106 <glossterm>Group IDentifier</glossterm>
107 <acronym>GID</acronym>
109 The UNIX system Group Identifier; on older systems, a 32-bit unsigned integer, and on
110 newer systems, an unsigned 64-bit integer. The GID is used in UNIX-like operating systems
111 for all group level access control.
116 <glossterm>Key Distribution Center</glossterm>
117 <acronym>KDC</acronym>
119 The Kerberos authentication protocol makes use of security keys (also called a ticket)
120 by which access to network resources is controlled. The issuing of Kerberos tickets
121 is effected by a KDC.
126 <glossterm>Light Weight Directory Access Protocol</glossterm>
127 <acronym>LDAP</acronym>
130 The Light Weight Directory Access Protocol is a technology that
131 originated from the development of X.500 protocol specifications and
132 implementations. LDAP was designed as a means of rapidly searching
133 through X.500 information. Later LDAP was adapted as an engine that
134 could drive its own directory database. LDAP is not a database per
135 se; rather it is a technology that enables high volume search and
136 locate activity from clients that wish to obtain simply defined
137 information about a sub-set of records that are stored in a
138 database. LDAP does not have a particularly efficient mechanism for
139 storing records in the database, and it has no concept of transaction
140 processing nor of mechanisms for preserving data consistency. LDAP is
141 premised around the notion that the search and read activity far
142 outweigh any need to add, delete, or modify records. LDAP does
143 provide a means for replication of the database so as to keep slave
144 servers up to date with a master. It also has built-in capability to
145 handle external references and deferral.
150 <glossterm>Local Master Browser</glossterm>
151 <acronym>LMB</acronym>
153 The Local Master Browser maintains a list of all servers that have announced themselves
154 within a given workgroup or NT domain on a particular broadcast isolated subnet.
159 <glossterm>Media Access Control</glossterm>
160 <acronym>MAC</acronym>
162 The hard-coded address of the physical layer device that is attached to the network.
163 All network interface controllers must have a hard-coded and unique MAC address. The
164 MAC address is 48 bits long.
169 <glossterm>NetBIOS Extended User Interface</glossterm>
170 <acronym>NetBEUI</acronym>
172 Very simple network protocol invented by IBM and Microsoft. It is used to do NetBIOS
173 over ethernet with low overhead. NetBEUI is a non-routable protocol.
178 <glossterm>Network Address Translation</glossterm>
179 <acronym>NAT</acronym>
181 Network address translation is a form of IP address masquerading. It ensures that internal
182 private (RFC1918) network addresses from packets inside the network are rewritten so
183 that TCP/IP packets that leave the server over a public connection are seen to come only
184 from the external network address.
189 <glossterm>Network Basic Input/Output System</glossterm>
190 <acronym>NetBIOS</acronym>
192 NetBIOS is a simple application programming interface (API) invented in the 1980s
193 that allows programs to send data to certain network names. NetBIOS is always run over
194 another network protocol such as IPX/SPX, TCP/IP, or Logical Link Control (LLC).
195 NetBIOS run over LLC is best known as NetBEUI (The NetBIOS Extended User Interface
196 &smbmdash; a complete misnomer!).
201 <glossterm>NetBT</glossterm>
202 <acronym>NBT</acronym>
204 Protocol for transporting NetBIOS frames over TCP/IP. Uses ports 137, 138, and 139.
205 NetBT is a fully routable protocol.
210 <glossterm>NT/LanManager Security Support Provider</glossterm>
211 <acronym>NTLMSSP</acronym>
213 The NTLM Security Support Provider (NTLMSSP) service in Windows NT4/200x/XP is responsible for
214 handling all NTLM authentication requests. It is the front end for protocols such as SPNEGO,
215 Schannel, and other technologies. The generic protocol family supported by NTLMSSP is known as
216 GSSAPI, the Generic Security Service Application Program Interface specified in RFC2078.
221 <glossterm>Server Message Block</glossterm>
222 <acronym>SMB</acronym>
224 SMB was the original name of the protocol spoken by Samba. It was invented in the 1980s
225 by IBM and adopted and extended further by Microsoft. Microsoft renamed the protocol to
226 CIFS during the Internet hype in the 1990s.
231 <glossterm>The Simple and Protected GSS-API Negotiation</glossterm>
232 <acronym>SPNEGO</acronym>
234 The purpose of SPNEGO is to allow a client and server to negotiate a security mechanism for
235 authentication. The protocol is specified in RFC2478 and uses tokens as built via ASN.1 DER.
236 DER refers to Distinguished Encoding Rules. These are a set of common rules for creating
237 binary encodings in a platform-independent manner. Samba has support for SPNEGO.
242 <glossterm>The Official Samba-3 HOWTO and Reference Guide</glossterm>
243 <acronym>TOSHARG</acronym>
245 This book makes repeated reference to <quote>The Official Samba-3 HOWTO and Reference Guide</quote>
246 by John H. Terpstra (Author) and Jelmer R. Vernooij (Author). This publication is available from
247 Amazon.com. Publisher: Prentice Hall PTR (October 2003),
253 <glossterm>User IDentifier</glossterm>
254 <acronym>UID</acronym>
256 The UNIX system User Identifier; on older systems, a 32-bit unsigned integer, and on newer systems,
257 an unsigned 64-bit integer. The UID is used in UNIX-like operating systems for all user level access
263 <glossterm>Universal Naming Convention</glossterm>
264 <acronym>UNC</acronym>
265 <glossdef><para>A syntax for specifying the location of network resources (such as file shares).
266 The UNC syntax was developed in the early days of MS DOS 3.x and is used internally by the SMB protocol.