From 8f8a9f01909ba29e2b781310baeeaaddc3f15f0d Mon Sep 17 00:00:00 2001 From: "Gerald W. Carter" Date: Tue, 22 Apr 2008 10:09:40 -0500 Subject: Moving docs tree to docs-xml to make room for generated docs in the release tarball. (This used to be commit 9f672c26d63955f613088489c6efbdc08b5b2d14) --- docs-xml/Samba4-HOWTO/ad-dc.xml | 4 + docs-xml/Samba4-HOWTO/ad-member.xml | 4 + docs-xml/Samba4-HOWTO/auth.xml | 4 + docs-xml/Samba4-HOWTO/cifsfs.xml | 4 + docs-xml/Samba4-HOWTO/compiling.xml | 24 ++++ docs-xml/Samba4-HOWTO/config.xml | 5 + docs-xml/Samba4-HOWTO/domain-bdc.xml | 4 + docs-xml/Samba4-HOWTO/domain-member.xml | 2 + docs-xml/Samba4-HOWTO/domain-pdc.xml | 1 + docs-xml/Samba4-HOWTO/gui-clients.xml | 1 + docs-xml/Samba4-HOWTO/history.xml | 0 docs-xml/Samba4-HOWTO/index.xml | 137 +++++++++++++++++++++ docs-xml/Samba4-HOWTO/ldb.xml | 1 + docs-xml/Samba4-HOWTO/printing.xml | 11 ++ docs-xml/Samba4-HOWTO/protocol.xml | 204 +++++++++++++++++++++++++++++++ docs-xml/Samba4-HOWTO/registry.xml | 4 + docs-xml/Samba4-HOWTO/samba.xml | 48 ++++++++ docs-xml/Samba4-HOWTO/security=share.xml | 8 ++ docs-xml/Samba4-HOWTO/security=user.xml | 6 + docs-xml/Samba4-HOWTO/shares.xml | 1 + docs-xml/Samba4-HOWTO/smbclient.xml | 4 + 21 files changed, 477 insertions(+) create mode 100644 docs-xml/Samba4-HOWTO/ad-dc.xml create mode 100644 docs-xml/Samba4-HOWTO/ad-member.xml create mode 100644 docs-xml/Samba4-HOWTO/auth.xml create mode 100644 docs-xml/Samba4-HOWTO/cifsfs.xml create mode 100644 docs-xml/Samba4-HOWTO/compiling.xml create mode 100644 docs-xml/Samba4-HOWTO/config.xml create mode 100644 docs-xml/Samba4-HOWTO/domain-bdc.xml create mode 100644 docs-xml/Samba4-HOWTO/domain-member.xml create mode 100644 docs-xml/Samba4-HOWTO/domain-pdc.xml create mode 100644 docs-xml/Samba4-HOWTO/gui-clients.xml create mode 100644 docs-xml/Samba4-HOWTO/history.xml create mode 100644 docs-xml/Samba4-HOWTO/index.xml create mode 100644 docs-xml/Samba4-HOWTO/ldb.xml create mode 100644 docs-xml/Samba4-HOWTO/printing.xml create mode 100644 docs-xml/Samba4-HOWTO/protocol.xml create mode 100644 docs-xml/Samba4-HOWTO/registry.xml create mode 100644 docs-xml/Samba4-HOWTO/samba.xml create mode 100644 docs-xml/Samba4-HOWTO/security=share.xml create mode 100644 docs-xml/Samba4-HOWTO/security=user.xml create mode 100644 docs-xml/Samba4-HOWTO/shares.xml create mode 100644 docs-xml/Samba4-HOWTO/smbclient.xml (limited to 'docs-xml/Samba4-HOWTO') diff --git a/docs-xml/Samba4-HOWTO/ad-dc.xml b/docs-xml/Samba4-HOWTO/ad-dc.xml new file mode 100644 index 0000000000..cdfc358edc --- /dev/null +++ b/docs-xml/Samba4-HOWTO/ad-dc.xml @@ -0,0 +1,4 @@ + + Active Directory - Domain Controller + + diff --git a/docs-xml/Samba4-HOWTO/ad-member.xml b/docs-xml/Samba4-HOWTO/ad-member.xml new file mode 100644 index 0000000000..b46d99be74 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/ad-member.xml @@ -0,0 +1,4 @@ + + Active Directory - Member + + diff --git a/docs-xml/Samba4-HOWTO/auth.xml b/docs-xml/Samba4-HOWTO/auth.xml new file mode 100644 index 0000000000..58b25f4035 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/auth.xml @@ -0,0 +1,4 @@ + + Authentication + + diff --git a/docs-xml/Samba4-HOWTO/cifsfs.xml b/docs-xml/Samba4-HOWTO/cifsfs.xml new file mode 100644 index 0000000000..190c3840d6 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/cifsfs.xml @@ -0,0 +1,4 @@ + + CIFSFS + + diff --git a/docs-xml/Samba4-HOWTO/compiling.xml b/docs-xml/Samba4-HOWTO/compiling.xml new file mode 100644 index 0000000000..048a0f4b8e --- /dev/null +++ b/docs-xml/Samba4-HOWTO/compiling.xml @@ -0,0 +1,24 @@ + + Compiling + + + Downloading the source - Tar Ball + + + + + Downloading the source - Subversion + + + + + Compiling the source + + + + + Installing + + + + diff --git a/docs-xml/Samba4-HOWTO/config.xml b/docs-xml/Samba4-HOWTO/config.xml new file mode 100644 index 0000000000..e251c698ab --- /dev/null +++ b/docs-xml/Samba4-HOWTO/config.xml @@ -0,0 +1,5 @@ + + Configuration + + Chapter describing Samba's configuration in detail. + diff --git a/docs-xml/Samba4-HOWTO/domain-bdc.xml b/docs-xml/Samba4-HOWTO/domain-bdc.xml new file mode 100644 index 0000000000..61c420fe7b --- /dev/null +++ b/docs-xml/Samba4-HOWTO/domain-bdc.xml @@ -0,0 +1,4 @@ + + Backup Domain Controller + + diff --git a/docs-xml/Samba4-HOWTO/domain-member.xml b/docs-xml/Samba4-HOWTO/domain-member.xml new file mode 100644 index 0000000000..8be3758792 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/domain-member.xml @@ -0,0 +1,2 @@ + + diff --git a/docs-xml/Samba4-HOWTO/domain-pdc.xml b/docs-xml/Samba4-HOWTO/domain-pdc.xml new file mode 100644 index 0000000000..b3fb6e6f7b --- /dev/null +++ b/docs-xml/Samba4-HOWTO/domain-pdc.xml @@ -0,0 +1 @@ + diff --git a/docs-xml/Samba4-HOWTO/gui-clients.xml b/docs-xml/Samba4-HOWTO/gui-clients.xml new file mode 100644 index 0000000000..0c50ccc8c6 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/gui-clients.xml @@ -0,0 +1 @@ + diff --git a/docs-xml/Samba4-HOWTO/history.xml b/docs-xml/Samba4-HOWTO/history.xml new file mode 100644 index 0000000000..e69de29bb2 diff --git a/docs-xml/Samba4-HOWTO/index.xml b/docs-xml/Samba4-HOWTO/index.xml new file mode 100644 index 0000000000..6562a7ed34 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/index.xml @@ -0,0 +1,137 @@ + + + + +The Official Samba-4 HOWTO + + + + &person.jelmer; + + + + + + + + + Attribution + + + + + + + + + + + + + Introduction to SMB networks + + Not everybody is already familiar with SMB networks and the jargon + used in such networks. This part describes the evolution of SMB, + how the protocol is structured and what Samba can be used for. + + NT admins, already familiar with SMB networks, are probably only + interested in the chapter about Samba itself. + + + + + + + + Samba 4 Basics + + FIXME + + + + + + + Network model + + + A SMB server is used in a certain network type + (workgroup, domain, active directory) with a specific + role (stand-alone, primary domain controller, backup domain controller, etc) in that network. Samba has to be configured according to that role. + Each of the chapters in this part describes how to configure Samba + for a specific role. + + + + + + Network Model: Share-based security + + + + + + Network Model: User-based security + + + + + Network Model: NT4-style domains + + + + + + + + + + Common services + + + Independent of the role the server has, it can provide services. + Examples of services are printing, user management, authentication, etc. + + + + + + + + + + Clients + + Samba includes a number of different clients for accessing + SMB file, print and other services. Pretty much every service can + be access using a command-line utility, though there are several + GUI clients available as well. + + + + + + + + Appendices + + + + + + + + + + + + + + + diff --git a/docs-xml/Samba4-HOWTO/ldb.xml b/docs-xml/Samba4-HOWTO/ldb.xml new file mode 100644 index 0000000000..5b1eb862e6 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/ldb.xml @@ -0,0 +1 @@ + diff --git a/docs-xml/Samba4-HOWTO/printing.xml b/docs-xml/Samba4-HOWTO/printing.xml new file mode 100644 index 0000000000..5ffb2b7680 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/printing.xml @@ -0,0 +1,11 @@ + + Printing + + + + + Unix printing types + + + + diff --git a/docs-xml/Samba4-HOWTO/protocol.xml b/docs-xml/Samba4-HOWTO/protocol.xml new file mode 100644 index 0000000000..f2961116e0 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/protocol.xml @@ -0,0 +1,204 @@ + + The SMB/CIFS protocol + + + + + "SMB" (also known as "CIFS") is a + file-sharing protocol that has been used since the mid-eighties. + Most people know SMB as the protocol behind the "Network Neighbourhood" + and remote printing in Windows. + + + + Several parts of the protocol are not discussed in this chapter, such + as mailslots, browsing and dfs, to prevent it from getting too complex. + CIFS internals are documented in detail in Hertel, 2003. + + + + + History + + + Invention by IBM + + + SMB is not very old, but it has a long history of modifications and extensions. + The original protocol was meant to run over ``NetBIOS'', which was the + name of the DOS interface to a very simple LAN system developed by IBM. + NetBIOS was developed because SNA, IBM's other main + protocol at the time, was much too advanced for use in DOS. + + + + The NetBIOS API in these days (early eighties) was nothing more then the + interface to a very simple link-layer protocol + over which several protocols, including SMB, were used. It could do reads and + writes to services on remote hosts, which were identified by case-insensitive + names, and discover all available hosts and services. + + + + Dr. Barry Feigenbau, an IBM employee, invented the core of the original SMB protocol, + which he initially named after himself: ``BAF''. He later changed the name to + be ``SMB'' (for ``Server Message Block''). Every packet in the protocol + starts with a byte $0xFF$ and these three letters. + + + + IBM, Microsoft, 3Com and Intel made up the rest of the initial protocol + together. The commands the protocol supported at this stage were basically + a mirror of the DOS File IO API calls, which meant the protocol wasn't very + efficient. The protocol also lacked authentication support. Everybody on the + network could do reads and writes, which meant this protocol + wasn't very suitable for large enterprises. + + + + NetBIOS is an API that has had various implementations; there is + NetBIOS over TCP/IP (NBT), NetBIOS over IPX, NetBIOS over SNA and + even NetBIOS over DECNEt. Mostly used these days is + NetBIOS over TCP (NBT). + + + + This is also were things are starting to get hairy. Since NetBIOS identifies + hosts by their name, NetBIOS clients had to start doing IP broadcasts to + figure out the IP of the host they had to connect to. Several schemes were + introduced to do name lookups crossing subnet boundaries, using name servers, + etc. We're basically emulating a NetBIOS LAN in order to be able to run SMB. + + + + Doing NetBIOS over IP is not very sane, however, the NBT implementation itself + in Windows isn't very nice either. It has horrible + limits, special exceptions, several broken schemes for looking up + names (including two kinds of name servers). NetBIOS and NetBIOS over TCP/IP + are described in RFC1001 and RFC1002. + + + + + The various incarnations of SMB + + Over the years, several usage models for SMB have been developed. While SMB originally started out as a file sharing protocol, it was later extended to include support for network management and other network services + as well. + + + One of the reasons for the various "upgrades" of the SMB + protocol is the fact that networks have become larger + and larger and with them the need for privilege separation + and scalability has increased. + + + + DOS + + + The original model in which SMB was used was as a + simple file-sharing service in a NetBIOS-environment. + + + + File sharing worked basically by specifying a list of directories that had + to be shared and what name they had to be shared under ("shares"). Eventually, + one could password-protect a share. At most one password per share could be set. + + + + + Windows For Workgroups + + + After the ``CORE'' dialect, + IBM and Microsoft implemented a new dialect known as ``LANMAN''. + This dialect was used by Windows for + Workgroups, OS/2 and Windows 9x which all know it under a different name. A + 'virtual' file system was also added, which was used for doing remote function + calls (RAP, for ``Remote Administration Protocol''). + + + + Computers are grouped into "Workgroups" in this model. Everybody is equal to + the others and there is no central point of control. + + + + + Windows NT + + For Windows NT, yet another dialect was added, named 'NT'. The NT dialect + had it's own set of file I/O functions (similar to the NT File I/O API) + and it had support for yet another way of doing remote function calls: + DCE/RPC. RPC's are used for DCOM and several of the subsystems in NT + that can be accessed remotely (registry, printing, user management, logging + on, etc). + + + + Windows NT works with a new concept for grouping computers called ``domains''In the protocol, domains are actually an upgraded version of a workgroup. Each computer is member of exactly one domain. There are several roles a computer can have in the domain: PDC (primary domain controller, the "manager" of the domain, that coordinates all authentication and authorization), BDC (Backup domain controller, in case the PDC goes down) or just a regular domain member. The PDC decides who is to be a member of the domain. + + + + + Windows 2000 + + In Windows NT 5 (marketing name: Windows 2000), NetBIOS-less SMB was + introduced. This means SMB is used directly over TCP port 445 instead of + via NetBIOS over TCP/IP. DNS + is used for looking up machine names. + + + Windows 2000 was also the first operating system from Microsoft + that had support for Active Directory. Active Directory is very + similar to the "domain" concept used by NT4, though it + is implemented differently (using modified open protocols), + and has some additional features (one of the most important ones being decentralized). + + + + Active directory no longer uses a central point of authority + and there are fewer limits to the size of a domain. Several + DC's can exist, so there is no longer a single point of + failure as well as better scalability. + + + + + + Samba versions and their support for the SMB models + + + Samba 2.2 + + Full CORE and Workgroup support. Somewhat basic + NT4-style support. + + + + Samba 3.0 + + Full CORE and Workgroup support. Almost complete + NT4-style support. + + + + + Samba 3.2 + + FIXME + + + + Samba 4.0 + + Full CORE, Workgroup, NT4 and ADS support. + + + + + diff --git a/docs-xml/Samba4-HOWTO/registry.xml b/docs-xml/Samba4-HOWTO/registry.xml new file mode 100644 index 0000000000..2ef11d3457 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/registry.xml @@ -0,0 +1,4 @@ + + Registry + + diff --git a/docs-xml/Samba4-HOWTO/samba.xml b/docs-xml/Samba4-HOWTO/samba.xml new file mode 100644 index 0000000000..8fed58559a --- /dev/null +++ b/docs-xml/Samba4-HOWTO/samba.xml @@ -0,0 +1,48 @@ + + Samba + + + Samba is an Open Source application that provides + an SMB implementation for POSIX-compatible + operating systems. + + + + Providing support for a Windows-based file-sharing protocol + on POSIX servers sometimes requires mapping Windows semantics to + POSIX semantics. + + + + Samba has always been catching up with Microsoft. Here is a list + of Samba releases and what they support (or will support). + + + + Samba 2.2 + + Full CORE and Workgroup support. Somewhat basic + NT4-style support. + + + + Samba 3.0 + + Full CORE and Workgroup support. Almost complete + NT4-style support. + + + + + Samba 3.2 + + FIXME + + + + Samba 4.0 + + Full CORE, Workgroup, NT4 and ADS support. + + + diff --git a/docs-xml/Samba4-HOWTO/security=share.xml b/docs-xml/Samba4-HOWTO/security=share.xml new file mode 100644 index 0000000000..1731bc0862 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/security=share.xml @@ -0,0 +1,8 @@ + + Share-based stand-alone server + + + One of the simplest + + + diff --git a/docs-xml/Samba4-HOWTO/security=user.xml b/docs-xml/Samba4-HOWTO/security=user.xml new file mode 100644 index 0000000000..1713c99c7c --- /dev/null +++ b/docs-xml/Samba4-HOWTO/security=user.xml @@ -0,0 +1,6 @@ + + User-based Stand-alone server + + + + diff --git a/docs-xml/Samba4-HOWTO/shares.xml b/docs-xml/Samba4-HOWTO/shares.xml new file mode 100644 index 0000000000..13e9b4c3dc --- /dev/null +++ b/docs-xml/Samba4-HOWTO/shares.xml @@ -0,0 +1 @@ + diff --git a/docs-xml/Samba4-HOWTO/smbclient.xml b/docs-xml/Samba4-HOWTO/smbclient.xml new file mode 100644 index 0000000000..1f97ce6265 --- /dev/null +++ b/docs-xml/Samba4-HOWTO/smbclient.xml @@ -0,0 +1,4 @@ + + smbclient + + -- cgit