ce707ecdaf
resolves: #1292069 CVE-2015-3223 Remote DoS in Samba (AD) LDAP server CVE-2015-5252 Insufficient symlink verification in smbd CVE-2015-5296 Samba client requesting encryption vulnerable to downgrade attack CVE-2015-5299 Missing access control check in shadow copy code CVE-2015-7540 DoS to AD-DC due to insufficient checking of asn1 memory allocation Guenther |
||
---|---|---|
.gitignore | ||
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.3.3-async_connect_send_test.patch | ||
samba.log | ||
samba.pamd | ||
samba.spec | ||
samba.xinetd | ||
smb.conf.default | ||
sources |
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.