Go to file
2016-05-25 10:40:41 +02:00
.gitignore Update to Samba 4.4.3 2016-05-02 17:37:57 +02:00
filter-requires-samba.sh
pam_winbind.conf
README.dc
README.downgrade
samba-4.2-auth-credentials-if-credentials-have-principal-set-t.patch
samba-4.4.2-s3-winbind-make-sure-domain-member-can-talk-to-trust.patch Update to Samba 4.4.2, fix badlock security bug 2016-04-12 19:34:47 +02:00
samba-use-libsystemd.patch Rebuild to drop libsystemd-daemon dependency 2016-05-23 09:26:33 -04:00
samba.log
samba.pamd
samba.spec Use %{_tmpfilesdir} macro 2016-05-25 10:40:41 +02:00
samba.xinetd
smb.conf.default
sources Update to Samba 4.4.3 2016-05-02 17:37:57 +02:00

Downgrading Samba
=================

Short version: data-preserving downgrades between Samba versions are not supported

Long version:
With Samba development there are cases when on-disk database format evolves.
In general, Samba Team attempts to maintain forward compatibility and
automatically upgrade databases during runtime when requires.
However, when downgrade is required Samba will not perform downgrade to
existing databases. It may be impossible if new features that caused database
upgrade are in use. Thus, one needs to consider a downgrade procedure before
actually downgrading Samba setup.

Please always perform back up prior both upgrading and downgrading across major
version changes. Restoring database files is easiest and simplest way to get to
previously working setup.

Easiest way to downgrade is to remove all created databases and start from scratch.
This means losing all authentication and domain relationship data, as well as
user databases (in case of tdb storage), printers, registry settings, and winbindd
caches.

Remove databases in following locations:
/var/lib/samba/*.tdb
/var/lib/samba/private/*.tdb

In particular, registry settings are known to prevent running downgraded versions
(Samba 4 to Samba 3) as registry format has changed between Samba 3 and Samba 4.