No description, website, or topics provided.
C Python Shell Perl XSLT Yacc Other
Pull request Compare This branch is 3 commits ahead, 4471 commits behind samba-team:master.
Latest commit 382b9db Mar 12, 2016 Andreas Gruenbacher vfs_richacl: Various fixes
SMB4ACL_T's don't support file masks, so when a richacl is exposed as a
SMB4ACL_T, the file masks need to be applied first.

Convert the (Automatic Inheritance-related) ACL flags.

Make sure the RICHACE_SPECIAL_WHO flag will not be set by accident.

Recognize additional errno values that can occur when richacls are not
supported.

Call add_implicitly_granted_permissions() when converting a richacl into
a SMB4ACL_T, not when converting a SMB4ACL_T into a richacl.
Permalink
Failed to load latest commit information.
auth auth/ntlmssp: remove ntlmssp_unwrap() fallback for LDAP Mar 10, 2016
buildtools configure: set HAVE___ATTRIBUTE__ for heimdal Mar 9, 2016
ctdb ctdb-client: Increase the timeout for TRANS3_COMMIT control Mar 11, 2016
dfs_server Avoid including libds/common/roles.h in public loadparm.h header. Jan 13, 2016
docs-xml Added MSV1_0_ALLOW_MSVCHAPV2 flag to ntlm_auth Mar 11, 2016
dynconfig build:wafsamba: Replace Options.is_install by bld.is_install Nov 16, 2015
examples s3: smbd: Change open_streams_for_delete() to take a struct smb_filen… Mar 7, 2016
file_server s4:server: avoid calling into nss_winbind from within 'samba' Jul 10, 2013
include build: added placeholder files for public header directories Mar 15, 2011
lib lib/util_net: add support for .ipv6-literal.net Mar 10, 2016
libcli ASN1: use a talloc context in read_contextSimple Mar 9, 2016
libds/common Avoid including libds/common/roles.h in public loadparm.h header. Jan 13, 2016
libgpo Fix various spelling errors Nov 6, 2015
librpc librpc/ndr: add ndr_ntlmssp_find_av() helper function Mar 10, 2016
nsswitch Added MSV1_0_ALLOW_MSVCHAPV2 flag to ntlm_auth Mar 11, 2016
packaging s3: smbd: Remove --with-aio-support. We no longer would ever prefer P… Nov 13, 2015
pidl pidl: Use a tmp_ctx helper variable Mar 8, 2016
python CVE-2016-0771: tests/dns: Remove dependencies on env variables Mar 10, 2016
release-scripts release-scripts/build-manpages-nogit: run make realdistclean at the end Aug 17, 2015
script script/release.sh: generate announce.${tagname}.patch.txt in announce… Feb 15, 2016
selftest selftest: mark samba4.winbind.struct.domain_info.ad_member as flapping Mar 12, 2016
source3 vfs_richacl: Various fixes Mar 13, 2016
source4 s4:dsdb/test/sort: avoid 'from collections import Counter' Mar 11, 2016
testdata KCC: add multisite ldif file for KCC tests May 30, 2015
testprogs selftest: add some test cases to net ads join Mar 10, 2016
tests lib: Remove sys_waitpid Feb 23, 2016
testsuite Simplify handling of dependencies on external libraries in test_headers. Jan 13, 2016
third_party thirdparty:waf: Update gccdeps from upstream Jan 2, 2016
wintest wintest: Try harder to make wintest force the telnet server to start Mar 14, 2014
.bzrignore Add bzrignore symlink. Dec 17, 2010
.gitignore .gitignore: Ignore pidl/MYMETA.json Apr 15, 2015
.testr.conf testr: Use waf testonly and create a custom directory for new workers. Oct 14, 2014
.travis.yml .travis.yml: install python3-{crypto,dev,dnspython} Feb 15, 2016
.ycm_extra_conf.py YouCompleteMe: Add missing path. Mar 20, 2015
BUILD_SYSTEMS.txt doc: Modify build doc concerning missing headers Jan 7, 2014
COPYING r23796: main COPYING file for samba4, plus some formatting varients Oct 10, 2007
Makefile Makefile: Add option to list all tests Sep 15, 2015
PFIF.txt Added PFIF notice to Samba 4.0 tree Jan 23, 2008
README Fix little typo in README file Dec 4, 2015
README.Coding README.Coding: Improve pointer example Feb 15, 2016
README.cifs-utils Update URL in README.cifs-utils Apr 2, 2010
README.contributing Update mailing list references to point at lists.samba.org Feb 10, 2015
Roadmap Update 4.2 Roadmap file May 21, 2015
VERSION VERSION: Bump version up to 4.5.0pre1 Jan 26, 2016
WHATSNEW.txt WHATSNEW: document removal of -P in smbget Feb 26, 2016
callcatcher-exceptions.grep build: Add exceptions for callcatcher unused function detection Feb 17, 2012
configure configure: Unload the wrappers so waf configure succeeds. Oct 9, 2014
configure.developer lib: Change socket_wrapper to preloadable version. Apr 17, 2014
install_with_python.sh install_with_python: Secure Python download with sha256 checks. Jul 24, 2015
prog_guide4.txt docs: Fix typo. Feb 18, 2013
upgrading-samba4.txt upgradedns: Rename to less generic name samba_upgradedns. Feb 24, 2012
wscript build: detect support for ethtool Jan 26, 2016
wscript_build codepages/*.dat are gone Mar 23, 2015
wscript_build_embedded_heimdal waf: move krb5 checks to a separate waf file Apr 23, 2012
wscript_build_system_heimdal waf: move krb5 checks to a separate waf file Apr 23, 2012
wscript_build_system_mitkrb5 waf: Use Logs.info() instead of print. Apr 17, 2012
wscript_configure_system_mitkrb5 wscript_configure_system_mitkrb5: add configure checks for GSS_KRB5_C… Mar 10, 2016

README

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
=============

1. To contribute via GitHub
  - fork the official Samba team repository on GitHub
      * see https://github.com/samba-team/samba
  - become familiar with the coding standards as described in README.Coding
  - make sure you read the Samba copyright policy
      * see https://www.samba.org/samba/devel/copyright-policy.html
  - create a feature branch
  - make changes
  - when committing, be sure to add signed-off-by tags
      * see https://wiki.samba.org/index.php/CodeReview#commit_message_tags
  - send a pull request for your branch through GitHub
  - this will trigger an email to the samba-technical mailing list
  - discussion happens on the samba-technical mailing list as described below
  - more info on using Git for Samba development can be found on the Samba Wiki
      * see https://wiki.samba.org/index.php/Using_Git_for_Samba_Development

2. 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 coordinate
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.