1
0
mirror of https://github.com/samba-team/samba.git synced 2024-12-23 17:34:34 +03:00
https://gitlab.com/samba-team/samba is the Official GitLab mirror of https://git.samba.org/samba.git -- Merge requests should be made on GitLab (not on GitHub)
Go to file
Stefan Metzmacher dc96b1ddcc libcli/auth: use unique key_name values in netlogon_creds_cli_context_common()
Until all callers are fixed to pass the same 'server_computer'
value, we try to calculate a server_netbios_name and use this
as unique identifier for a specific domain controller.

Otherwise winbind would use 'hostname.example.com'
while 'net rpc testjoin' would use 'HOSTNAME',
which leads to 2 records in netlogon_creds_cli.tdb
for the same domain controller.

Once all callers are fixed we can think about reverting this
commit.

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
2014-01-07 12:47:04 +01:00
auth auth/gensec: implement GENSEC_FEATURE_SIGN_PKT_HEADER in schannel.c 2014-01-07 00:27:11 +01:00
buildtools waf: parse LDFLAGS from python 2013-10-25 02:48:35 +02:00
codepages
ctdb ctdb/eventscripts: Do not reconfigure in "monitor" events 2013-12-17 06:32:35 +01:00
dfs_server dfs_server: Use dsdb_search_one to catch 0 results as well as NO_SUCH_OBJECT errors 2013-08-02 13:11:20 +02:00
docs-xml docs: Add num-children to smbcontrol manpage 2014-01-06 23:20:24 +01:00
dynconfig dynconfig: Remove last s3 markers now we have just one build system 2013-07-24 16:29:15 +02:00
examples vfs: add [GET/SET]_COMPRESSION hooks 2013-11-22 08:56:45 -08:00
file_server s4:server: avoid calling into nss_winbind from within 'samba' 2013-07-10 23:18:06 +02:00
include
lib waf: Fix the FreeBSD build with libinotify 2014-01-06 19:50:22 +01:00
libcli libcli/auth: use unique key_name values in netlogon_creds_cli_context_common() 2014-01-07 12:47:04 +01:00
libds/common lib/param: Create a seperate server role for "active directory domain controller" 2012-06-15 09:18:33 +02:00
libgpo libgpo: remove unused process_group_policy2 callback from CSE module API. 2013-12-18 16:45:20 +01:00
librpc librpc/rpc: read the full header in dcerpc_read_ncacn_packet_next_vector() 2014-01-07 08:37:36 +01:00
nsswitch CVE-2013-4408:s3:Ensure LookupSids replies arrays are range checked. 2013-12-09 07:05:46 +01:00
packaging Remove remaining references to "password level" in the tree 2013-06-11 16:25:54 +02:00
pidl pidl:NDR/Client: avoid useless memcpy() 2014-01-07 08:37:38 +01:00
python netcmd/dns: Catch wildcard patterns when querying for name 2013-11-30 14:22:57 +11:00
release-scripts build-htmlman-nogit: Run build-htmlman-nogit with bash. 2013-05-30 04:48:06 +02:00
script autobuild: Run ctdb regression tests 2013-11-28 07:31:13 +01:00
selftest selftest: pass -l logdir to daemon processes. 2013-12-11 17:22:40 +01:00
source3 libcli/smb: s/tstream_cli_np/tstream_smbXcli_np 2014-01-07 08:37:42 +01:00
source4 s4:librpc: remove recv_data from transport 2014-01-07 12:42:32 +01:00
testdata s4-samldb: Do not allow deletion of objects with RID < 1000 2013-10-14 13:31:50 +02:00
testprogs midltests: add tests with v1_enum and NDR64 2014-01-07 08:37:38 +01:00
tests build: Fix quota tests, including move of sysquotas.c to the top level 2012-09-29 14:50:00 +10:00
testsuite testsuit: Fix fprintf format. 2013-11-15 11:07:40 -08:00
wintest wintest: Try harder to recover from apparent failure to dcpromo 2012-11-06 08:27:44 +11:00
.bzrignore
.clang_complete misc: Add a config for clang complete. 2012-12-12 13:15:00 +01:00
.gitignore .gitignore: Tidy up after removal of the autoconf build 2013-06-10 04:42:46 +02:00
.testr.conf testr: Use test lists. 2011-11-30 22:58:04 +01:00
BUILD_SYSTEMS.txt doc: Modify build doc concerning missing headers 2014-01-07 04:13:27 +01:00
callcatcher-exceptions.grep build: Add exceptions for callcatcher unused function detection 2012-02-17 09:12:47 +01:00
configure configure: Support specifying PYTHON environment variable to run waf. 2012-11-09 14:54:46 +01:00
configure.developer
COPYING
install_with_python.sh build: Do not set PATH in install_with_python now we set $PYTHON 2013-05-16 19:02:01 +02:00
MAINTAINERS.txt Add myself as libcli/dns maintainer 2012-05-30 00:38:00 +02:00
Makefile Makefile: Allow specifying PYTHON environment variable. 2012-11-09 16:39:09 +01:00
PFIF.txt
prog_guide4.txt docs: Fix typo. 2013-02-18 22:07:39 +11:00
README docs: Move Samba4 HOWTO link into README 2012-09-04 03:05:02 +02:00
README.cifs-utils
README.Coding README.Coding: Add __func__ 2013-11-11 16:08:09 +01:00
README.contributing
README.packaging4
Roadmap docs: Update Roadmap 2012-09-04 09:31:49 +10:00
upgrading-samba4.txt upgradedns: Rename to less generic name samba_upgradedns. 2012-02-24 15:07:25 +01:00
VERSION VERSION: change to 4.2.0pre1 2013-07-05 12:34:19 +02:00
WHATSNEW.txt WHATSNEW: Fix 4.0 default for allow dns updates. 2013-06-01 18:54:06 +10:00
wscript waf: Build with RELRO if supported by the compiler. 2013-07-09 13:00:37 -07:00
wscript_build Move python modules from source4/scripting/python/ to python/. 2013-03-02 03:57:34 +01:00
wscript_build_embedded_heimdal waf: move krb5 checks to a separate waf file 2012-04-23 16:38:43 -04:00
wscript_build_system_heimdal waf: move krb5 checks to a separate waf file 2012-04-23 16:38:43 -04:00
wscript_build_system_mitkrb5 waf: Use Logs.info() instead of print. 2012-04-17 17:48:23 +02:00
wscript_configure_system_mitkrb5 wafbuild: use WERROR_FLAGS in wscript_configure_system_mitkrb5 2012-10-30 13:18:50 +01:00

This is the release version of Samba, the free SMB and CIFS client and
server and Domain Controller for UNIX and other operating
systems. Samba is maintained by the Samba Team, who support the
original author, Andrew Tridgell.

>>>> Please read THE WHOLE of this file as it gives important information
>>>> about the configuration and use of Samba.

NOTE: Installation instructions may be found
      for the file/print server and domain member in:
      docs/htmldocs/Samba3-HOWTO/install.html

      For the AD DC implementation a full HOWTO is provided at:
      http://wiki.samba.org/index.php/Samba4/HOWTO

This software is freely distributable under the GNU public license, a
copy of which you should have received with this software (in a file
called COPYING). 


WHAT IS SMB/CIFS?
=================

This is a big question. 

The very short answer is that it is the protocol by which a lot of
PC-related machines share files and printers and other information
such as lists of available files and printers. Operating systems that
support this natively include Windows 9x, Windows NT (and derivatives), 
OS/2, Mac OS X and Linux.  Add on packages that achieve the same 
thing are available for DOS, Windows 3.1, VMS, Unix of all kinds, 
MVS, and more.  Some Web Browsers can speak this protocol as well 
(smb://).  Alternatives to SMB include Netware, NFS, Appletalk, 
Banyan Vines, Decnet etc; many of these have advantages but none are 
both public specifications and widely implemented in desktop machines 
by default.

The Common Internet File system (CIFS) is what the new SMB initiative
is called. For details watch http://samba.org/cifs.


WHY DO PEOPLE WANT TO USE SMB?
==============================

1. Many people want to integrate their Microsoft desktop clients
   with their Unix servers.

2. Others want to integrate their Microsoft (etc) servers with Unix
   servers. This is a different problem to integrating desktop 
   clients.

3. Others want to replace protocols like NFS, DecNet and Novell NCP,
   especially when used with PCs.


WHAT CAN SAMBA DO?
==================

Please refer to the WHATSNEW.txt included with this README for
a list of features in the latest Samba release.

Here is a very short list of what samba includes, and what it does. 
For many networks this can be simply summarized by "Samba provides 
a complete replacement for Windows NT, Warp, NFS or Netware servers."

- a SMB server, to provide Windows NT and LAN Manager-style file and print 
  services to SMB clients such as Windows 95, Warp Server, smbfs and others.

- a Windows Domain Controller (NT4 and AD) replacement.

- a file/print server that can act as a member of a Windows NT 4.0
  or Active Directory domain.

- a NetBIOS (rfc1001/1002) nameserver, which amongst other things gives 
  browsing support. Samba can be the master browser on your LAN if you wish.

- a ftp-like SMB client so you can access PC resources (disks and
  printers) from UNIX, Netware, and other operating systems

- a tar extension to the client for backing up PCs

- limited command-line tool that supports some of the NT administrative
  functionality, which can be used on Samba, NT workstation and NT server.

For a much better overview have a look at the web site at
http://samba.org/samba, and browse the user survey.

Related packages include:

- cifsvfs, an advanced Linux-only filesystem allowing you to mount 
  remote SMB filesystems from PCs on your Linux box. This is included 
  as standard with Linux 2.5 and later.

- smbfs, the previous Linux-only filesystem allowing you to mount remote SMB
  filesystems from PCs on your Linux box. This is included as standard with
  Linux 2.0 and later.



CONTRIBUTIONS
=============

If you want to contribute to the development of the software then
please join the mailing list. The Samba team accepts patches
(preferably in "diff -u" format, see http://samba.org/samba/devel/ 
for more details) and are always glad to receive feedback or 
suggestions to the address samba@lists.samba.org.  More information
on the various Samba mailing lists can be found at http://lists.samba.org/.

You can also get the Samba sourcecode straight from the git repository - see
http://wiki.samba.org/index.php/Using_Git_for_Samba_Development.

If you like a particular feature then look through the git change-log
(on the web at http://gitweb.samba.org/?p=samba.git;a=summary) and see
who added it, then send them an email.

Remember that free software of this kind lives or dies by the response
we get. If no one tells us they like it then we'll probably move onto
something else.

MORE INFO
=========

DOCUMENTATION
-------------

There is quite a bit of documentation included with the package,
including man pages, and lots of .html files with hints and useful
info. This is also available from the web page. There is a growing
collection of information under docs/.

A list of Samba documentation in languages other than English is
available on the web page.

If you would like to help with the documentation, please coodinate 
on the samba@samba.org mailing list.  See the next section for details 
on subscribing to samba mailing lists.


MAILING LIST
------------

Please do NOT send subscription/unsubscription requests to the lists!

There is a mailing list for discussion of Samba.  For details go to
<http://lists.samba.org/> or send mail to <samba-subscribe@lists.samba.org>

There is also an announcement mailing list where new versions are
announced.  To subscribe go to <http://lists.samba.org/> or send mail
to <samba-announce-subscribe@lists.samba.org>.  All announcements also
go to the samba list, so you only need to be on one.

For details of other Samba mailing lists and for access to archives, see
<http://lists.samba.org/>


MAILING LIST ETIQUETTE
----------------------

A few tips when submitting to this or any mailing list.

1. Make your subject short and descriptive. Avoid the words "help" or
   "Samba" in the subject. The readers of this list already know that
   a) you need help, and b) you are writing about samba (of course,
   you may need to distinguish between Samba PDC and other file
   sharing software). Avoid phrases such as "what is" and "how do
   i". Some good subject lines might look like "Slow response with
   Excel files" or "Migrating from Samba PDC to NT PDC".

2. If you include the original message in your reply, trim it so that
   only the relevant lines, enough to establish context, are
   included. Chances are (since this is a mailing list) we've already
   read the original message.

3. Trim irrelevant headers from the original message in your
   reply. All we need to see is a) From, b) Date, and c) Subject. We
   don't even really need the Subject, if you haven't changed
   it. Better yet is to just preface the original message with "On
   [date] [someone] wrote:".

4. Please don't reply to or argue about spam, spam filters or viruses
   on any Samba lists. We do have a spam filtering system that is
   working quite well thank you very much but occasionally unwanted
   messages slip through. Deal with it.

5. Never say "Me too." It doesn't help anyone solve the
   problem. Instead, if you ARE having the same problem, give more
   information. Have you seen something that the other writer hasn't
   mentioned, which may be helpful?

6. If you ask about a problem, then come up with the solution on your
   own or through another source, by all means post it. Someone else
   may have the same problem and is waiting for an answer, but never
   hears of it.

7. Give as much *relevant* information as possible such as Samba
   release number, OS, kernel version, etc...

8. RTFM. Google. groups.google.com.


WEB SITE
--------

A Samba WWW site has been setup with lots of useful info. Connect to:

http://samba.org/

As well as general information and documentation, this also has searchable 
archives of the mailing list and a user survey that shows who else is using
this package.