1d03aa069e
These patches are part of the https://gitlab.com/samba-redhat/samba/-/tree/v4-13-redhat [PATCH 001/105] libcli:smb2: Do not leak ptext on error [PATCH 002/105] libcli:smb2: Use talloc NULL context if we don't have [PATCH 003/105] auth:creds: Introduce CRED_SMB_CONF [PATCH 004/105] param: Add 'server smb encrypt' parameter [PATCH 005/105] param: Create and use enum_smb_encryption_vals [PATCH 006/105] s3:smbd: Use 'enum smb_encryption_setting' values [PATCH 007/105] docs-xml: Add 'client smb encrypt' [PATCH 008/105] lib:param: Add lpcfg_parse_enum_vals() [PATCH 009/105] libcli:smb: Add smb_signing_setting_translate() [PATCH 010/105] libcli:smb: Add smb_encryption_setting_translate() [PATCH 011/105] s3:lib: Use smb_signing_setting_translate for cmdline [PATCH 012/105] auth:creds: Remove unused credentials autoproto [PATCH 013/105] auth:creds: Add [PATCH 014/105] auth:creds: Add python bindings for [PATCH 015/105] auth:creds: Add [PATCH 016/105] auth:creds: Add python bindings for [PATCH 017/105] auth:creds: Add [PATCH 018/105] auth:creds: Add python bindings for [PATCH 019/105] auth:creds: Add python bindings for [PATCH 020/105] auth:creds: Bump library version [PATCH 021/105] s3:lib: Use cli_credential_(get|set)_smb_signing() [PATCH 022/105] s3:lib: Set smb encryption also via cli creds API [PATCH 023/105] python: Remove unused sign argument from [PATCH 024/105] python: Set smb signing via the creds API [PATCH 025/105] s3:libsmb: Introduce CLI_FULL_CONNECTION_IPC [PATCH 026/105] s3:pylibsmb: Add ipc=True support for [PATCH 027/105] python:tests: Mark libsmb connection as an IPC [PATCH 028/105] python:tests: Set smb ipc signing via the creds API [PATCH 029/105] s3:libsmb: Use 'enum smb_signing_setting' in [PATCH 030/105] s3:client: Turn off smb signing for message op [PATCH 031/105] s3:libsmb: Remove signing_state from [PATCH 032/105] s3:libsmb: Remove signing_state from [PATCH 033/105] s3:libsmb: Add encryption support to [PATCH 034/105] python: Add a test for SMB encryption [PATCH 035/105] s3:net: Use cli_credentials_set_smb_encryption() [PATCH 036/105] s3:libsmb: Use cli_credentials_set_smb_encryption() [PATCH 037/105] s3:client: Remove unused smb encryption code [PATCH 038/105] s3:utils: Remove obsolete force encryption from [PATCH 039/105] s3:utils: Remove obsolete force encryption from [PATCH 040/105] s3:utils: Remove obsolete force encryption from [PATCH 041/105] s3:rpcclient: Remove obsolete force encryption from [PATCH 042/105] examples: Remove obsolete force encryption from [PATCH 043/105] s3:libsmb: Make cli_cm_force_encryption_creds() [PATCH 044/105] s4:libcli: Return NTSTATUS errors for [PATCH 045/105] s4:libcli: Return if encryption is requested for SMB1 [PATCH 046/105] s3:libcli: Split out smb2_connect_tcon_start() [PATCH 047/105] s4:libcli: Add smb2_connect_enc_start() [PATCH 048/105] s4:libcli: Require signing for SMB encryption [PATCH 049/105] python:tests: Add test for SMB encrypted DCERPC [PATCH 050/105] auth:gensec: Add gensec_security_sasl_names() [PATCH 051/105] s4:ldap_server: Use samba_server_gensec_start() in [PATCH 052/105] auth:gensec: Make gensec_use_kerberos_mechs() a [PATCH 053/105] auth:gensec: Pass use_kerberos and keep_schannel to [PATCH 054/105] auth:gensec: If Kerberos is required, keep schannel [PATCH 055/105] auth:creds: Add cli_credentials_init_server() [PATCH 056/105] s4:rpc_server: Use cli_credentials_init_server() [PATCH 057/105] s4:smb_server: Use cli_credentials_init_server() for [PATCH 058/105] selftest: Rename 'smb encrypt' to 'server smb [PATCH 059/105] selftest: Move enc_desired to provision to have it in [PATCH 060/105] s3:tests: Add smbclient tests for 'client smb [PATCH 061/105] s3:client: Remove global smb_encrypt [PATCH 062/105] s3:libsmb: Remove force_encrypt from cli_cm_open() [PATCH 063/105] s3:libsmb: Remove force_encrypt from cli_cm_connect() [PATCH 064/105] s3:libsmb: Remove force_encrypt from clidfs [PATCH 065/105] s3:libsmb: Remove force_encrypt from [PATCH 066/105] s3:libsmb: Pass cli_credentials to clidfs [PATCH 067/105] s3:libsmb: Pass cli_credentials to cli_cm_connect() [PATCH 068/105] s3:libsmb: Pass cli_credentials to cli_cm_open() [PATCH 069/105] s3:libsmb: Pass cli_credentials to [PATCH 070/105] s3:client: Remove global max_protocol [PATCH 071/105] s3:libsmb: Remove max_protocol from cli_cm_open() [PATCH 072/105] s3:libcmb: Remove max_protocol from cli_cm_connect() [PATCH 073/105] s3:libsmb: Remove max_protocol from clidfs [PATCH 074/105] s3:include: Move loadparm prototypes to own header [PATCH 075/105] s3:lib: Move interface prototypes to own header file [PATCH 076/105] idl: Add SID_SAMBA_SMB3 [PATCH 077/105] s3:smbd: Add SMB3 connection information to session [PATCH 078/105] librpc: Add dcerpc helper [PATCH 079/105] s3:smbd: Use defines to set 'srv_smb_encrypt' [PATCH 080/105] s3:rpc_server: Allow to use RC4 for setting passwords [PATCH 081/105] s4:rpc_server: Allow to use RC4 for setting passwords [PATCH 082/105] lib:crypto: Add py binding for set_relax/strict fips [PATCH 083/105] s4:param: Add 'weak crypto' getter to pyparam [PATCH 084/105] python:tests: Add SAMR password change tests for fips [PATCH 085/105] python:tests: Add SAMR password change tests for fips [PATCH 086/105] auth:creds: Rename CRED_USE_KERBEROS values [PATCH 087/105] auth:creds:tests: Migrate test to a cmocka unit test [PATCH 088/105] s3-vfs_glusterfs: always disable write-behind [PATCH 089/105] Add smb2cli_session_get_encryption_cipher() [PATCH 090/105] Add dcerpc_transport_encrypted() [PATCH 091/105] Add py binding for dcerpc_transport_encrypted [PATCH 092/105] selftest: add a test for py dce transport_encrypted [PATCH 093/105] Add CreateTrustedDomainRelax wrapper for fips mode [PATCH 094/105] Use the new CreateTrustedDomainRelax() [PATCH 095/105] selftest: add a test for the CreateTrustedDomainRelax [PATCH 096/105] Remove source4/scripting/devel/createtrust script [PATCH 097/105] s3:rpc_server: Use gnutls_cipher_decrypt() in [PATCH 098/105] s4:rpc_server: Use gnutls_cipher_decrypt() in [PATCH 099/105] s3:rpc_server: Allow to use RC4 for creating trusts [PATCH 100/105] s4:rpc_server: Allow to use RC4 for creating trusts [PATCH 101/105] sefltest: Enable the dcerpc.createtrustrelax test [PATCH 102/105] s3: spoolss: Make parameters in call to [PATCH 103/105] s3:smbd: Fix possible null pointer dereference in [PATCH 104/105] lookup_name: allow lookup names prefixed with DNS [PATCH 105/105] auth_sam: use pdb_get_domain_info to look up DNS |
||
|---|---|---|
| .gitignore | ||
| filter-requires-samba.sh | ||
| gpgkey-52FBC0B86D954B0843324CDC6F33915B6568B7EA.gpg | ||
| pam_winbind.conf | ||
| README.downgrade | ||
| README.md | ||
| samba-4.13-redhat.patch | ||
| samba-s4u.patch | ||
| samba-smbclient-mget-bug-14517.patch | ||
| samba.logrotate | ||
| samba.pamd | ||
| samba.spec | ||
| smb.conf.example | ||
| smb.conf.vendor | ||
| sources | ||
Samba is a free SMB and CIFS client and server and Domain Controller for UNIX and other operating systems. It is maintained by the Samba Team, who support the original author, Andrew Tridgell.
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 here
WHY DO PEOPLE WANT TO USE SMB?
-
Many people want to integrate their Microsoft desktop clients with their Unix servers.
-
Others want to integrate their Microsoft (etc) servers with Unix servers. This is a different problem to integrating desktop clients.
-
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 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
To contribute via GitHub
-
fork the official Samba team repository on GitHub -- see GitHub
-
become familiar with the coding standards as described in README.Coding
-
make sure you read the Samba copyright policy -- see Copyright Policy
-
create a feature branch
-
make changes
-
when committing, be sure to add signed-off-by tags -- see 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 Samba Wiki -- see Using Git for Samba
To contribute via mailing lists
Join the mailing list. The Samba team accepts patches (preferably in "diff -u" format, see here 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 mailman.
You can also get the Samba sourcecode straight from the git repository.
If you like a particular feature then look through the git change-log on the web 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@lists.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 mailman 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 mailman 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 mailman
MAILING LIST ETIQUETTE
A few tips when submitting to this or any mailing list.
-
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".
-
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.
-
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:".
-
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.
-
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?
-
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.
-
Give as much relevant information as possible such as Samba release number, OS, kernel version, etc...
-
RTFM. Google.
WEB SITE
A Samba WWW site has been setup with lots of useful info.
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.