Search results

From SambaWiki
  • | text = This page describes creating a backup on Samba v4.9 onwards. For backups on Samba v4.0-v4.8, see [[Using_the_samb ...in the unlikely event that it suffers a catastrophic failure. It does not backup individual DCs.
    24 KB (4,038 words) - 09:39, 17 March 2021
  • ...as Microsoft Active Directory. Schema updates in AD are a sensitive action and you must be prepared to do a [[Back_up_and_Restoring_a_Samba_AD_DC|full res ...true in Samba 4 given it does fully validate all the changes to the schema and so some changes can lead to a un-start-able samba provision.
    10 KB (1,486 words) - 09:54, 30 March 2024
  • ...method is described in more detail [[Upgrading_a_Samba_AD_DC#Upgrade A DC and join it to the domain again|here]]. ...ts of the database. Changes to the database format were introduced in v4.8 and v4.11.
    11 KB (1,744 words) - 21:11, 12 November 2022
  • ...ation changes to continue to talk to domain controllers (see "file servers and domain members" below). ...name=CVE-2020-1472 CVE-2020-1472]. Since the bug is a protocol level flaw, and Samba implements the protocol, Samba is also vulnerable.
    63 KB (9,242 words) - 20:37, 22 September 2020
  • ...nix and Linux) compatibility for the current SMB3 version of the protocol, and current protocol extensions, are described here: [[SMB3-Linux|SMB3 POSIX Ex (via a Unix QueryFSInfo and SetFSInfo level). Following
    20 KB (2,959 words) - 20:18, 30 November 2022
  • :The implementation of ACL inheritance in the Samba AD DC was not complete, and so absent a 'full-sync' replication, ACLs could get out of sync between dom For more details and workarounds, please refer to the security advisories.
    76 KB (11,334 words) - 15:03, 3 March 2020
  • :A man in the middle attack can read and may alter confidential documents transferred via a client connection, which For more details and workarounds, please see the security advisories:
    78 KB (11,799 words) - 22:01, 17 September 2019