Developer Documentation: Difference between revisions

From SambaWiki
(use include for Samba codebase organization)
(11 intermediate revisions by 3 users not shown)
Line 27: Line 27:
* [https://github.com/samba-team/samba Official Samba GitHub Mirror]
* [https://github.com/samba-team/samba Official Samba GitHub Mirror]


== Samba codebase organization ==


{{:Samba codebase organization overview}}

The Samba codebase is broken down in detail in the '''[[Samba_codebase_organization|Samba codebase organization page]]'''.


= Debugging / Testing =
= Debugging / Testing =
Line 33: Line 37:
* [[The_Samba_Selftest_System|The Samba Selftest System]]
* [[The_Samba_Selftest_System|The Samba Selftest System]]


* [[CI using Your own gitlab runner]]
* [[Samba CI on gitlab]]

== [[Writing_Tests|Writing and running Samba tests]]==


* [[Writing_Torture_Tests|Writing Torture Tests]]
* [[Writing_Torture_Tests|Writing Torture Tests]]
Line 47: Line 53:
* [[WinTest|Testing against Windows using WinTest]]
* [[WinTest|Testing against Windows using WinTest]]


* [[Understanding_make_test|Understanding make test]]
* [[Testing_development_trees|Testing development trees]]


== Debugging help ==
* [[Debugging_individual_tests|Debugging individual tests]]


* [[Keytab_Extraction|Keytab extraction]]
* [[Keytab_Extraction|Keytab extraction]]
Line 58: Line 64:


* [[Saving_RPC_FAULTs|Saving packets that failed to parse to test IDL fixes using ndrdump]]
* [[Saving_RPC_FAULTs|Saving packets that failed to parse to test IDL fixes using ndrdump]]

* [[Python/Debugging|Debugging in Python]]

== Development testing ==

* [[Testing removal of ifdef or configure checks|Testing removal of #ifdef or configure checks]]
* [[Fuzzing|Information on Samba's fuzzing infrastructure]]


= Bug reporting =
= Bug reporting =
Line 66: Line 79:




= Security =

* [[Samba_Security_Documentation|Samba Security Documentation]]
* [[Samba_Protocol_Security|Samba Protocol Security Layers]]


= Presentations =
= Presentations =
Line 128: Line 145:


* [[Samba4/ActiveDirectory|Active Directory Plans]]
* [[Samba4/ActiveDirectory|Active Directory Plans]]

* [[Samba4/LDAP_Backend|LDAP Directory Server Backend History Notes]]


* [[Samba4 AD Plugfest 2010 TODO list|Samba 4 AD Plugfest 2010 TODO List]]
* [[Samba4 AD Plugfest 2010 TODO list|Samba 4 AD Plugfest 2010 TODO List]]


* [http://download.samba.org/pub/samba/rc/ Development Releases of Samba4 (technology previews, alphas, betas, release candidates)]
* [http://download.samba.org/pub/samba/rc/ Development Releases of Samba4 (technology previews, alphas, betas, release candidates)]




= Academic Writings etc. =
= Academic Writings etc. =

Revision as of 22:02, 12 June 2020

How can I contribute


Release planning


Source code

Samba development is stored in the Git SCM system. See Using Git for Samba Development for more detail on how Samba uses Git.

Two web interfaces are:

Samba codebase organization

Broadly speaking, the Samba source-code tree can be organized into the following major groups:

  • Top-level libraries, which contains common code shared amongst the Samba processes.
  • Source3, which is code primarily used by the file server and domain member.
  • Source4, which is code primarily used by the Active Directory Domain Controller.
  • Infrastructure components, which provide the build and test framework for Samba.
  • Autogenerated code, which is used for parsing DCE/RPC packets as well as other regularly structured buffers.

The Samba codebase is broken down in detail in the Samba codebase organization page.

Debugging / Testing

Writing and running Samba tests

Debugging help

Development testing

Bug reporting


Security

Presentations


VFS


Clustered Samba

Building Samba


Building packages


Google Summer of Code


Historical Documentation on the Development of Samba4

  • Franky: A Hybrid Samba Active Directory Controller (outdated!)

Academic Writings etc.