Go to file
2017-03-28 14:04:15 +02:00
.gitignore Update to Samba 4.6.1 2017-03-23 11:20:02 +01:00
filter-requires-samba.sh Fix and mention bogus perl dependency removal. 2009-02-03 18:45:43 +00:00
gpgkey-52FBC0B86D954B0843324CDC6F33915B6568B7EA.gpg Verify the tarball with the gpg key and amror file from Samba 2017-02-01 15:34:35 +01:00
pam_winbind.conf Update to 3.3.4 2009-04-29 14:26:55 +00:00
README.dc Update README.dc. 2012-11-19 14:34:27 +01:00
README.downgrade Update to 4.0.0rc1. 2012-09-26 14:23:24 +02:00
samba-v4.6-credentials-fix-realm.patch one more patch from git master 2017-03-10 19:47:24 +02:00
samba-v4.6-gss_krb5_import_cred.patch credentials_krb5: use gss_acquire_cred for client-side GSSAPI use case 2017-03-09 16:36:37 +02:00
samba-v4.6-lib-crypto-implement-samba.crypto-Python-module-for-.patch export arcfour_crypt_blob to Python as samba.crypto.arcfour_encrypt 2017-03-15 13:47:49 +02:00
samba.log * Wed Oct 8 2007 Simo Sorce <ssorce@redhat.com> 3.2.0-0.pre1.fc9 2007-10-08 21:13:15 +00:00
samba.pamd Update to Samba 4.0.0rc6. 2012-12-04 15:38:51 +01:00
samba.spec Only require cmocka for the testsuite build 2017-03-28 14:04:15 +02:00
smb.conf.example Small fix to the example smb.conf file 2016-06-20 09:41:05 +02:00
smb.conf.vendor Update to Samba 4.4.4 2016-06-07 14:36:53 +02:00
sources Update to Samba 4.6.1 2017-03-23 11:20:02 +01: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.