Samba RPM rebuilt on el7 with DC support
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Daniel Berteaud 57f9f00226 Automatic commit of package [samba] minor release [4.8.3-101.dc]. 2 months ago
.tito Automatic commit of package [samba] minor release [4.8.3-101.dc]. 2 months ago
.gitattributes Switch to GitLfsBuilder 7 months ago
.gitignore Rebase on upstream 4.7.1 1 year ago
CVE-2018-1139.patch Rebase on 4.8.3 7 months ago
CVE-2018-10858.patch Rebase on 4.8.3 7 months ago
README.dc Initial import 1 year ago
README.downgrade Initial import 1 year ago
gpgkey-52FBC0B86D954B0843324CDC6F33915B6568B7EA.gpg Initial import 1 year ago
pam_winbind.conf Initial import 1 year ago
samba-4.8.3-fix_krb5_plugins.patch Rebase on 4.8.3 7 months ago
samba-4.8.3-fix_winbind_getpwnam_local_user.patch Rebase on 4.8.3 7 months ago
samba-4.8.3-smbclient_quiet_argument.patch Rebase on 4.8.3 7 months ago
samba-4.8.3.tar.asc Rebase on 4.8.3 7 months ago
samba-4.8.3.tar.xz Rebase on 4.8.3 7 months ago
samba.log Initial import 1 year ago
samba.pamd Initial import 1 year ago
samba.spec Automatic commit of package [samba] minor release [4.8.3-101.dc]. 2 months ago
smb.conf.example Initial import 1 year ago
smb.conf.vendor Rebase on upstream 4.7.1 1 year ago

README.downgrade

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.