Samba4 is an attempt to implement an Active Directory compatible Domain
Controller.
In short, you can join a WinNT, Win2000, WinXP or Win 2003 - 2016 member
server to a Samba4 domain, and it will behave much as it does in AD,
including Kerberos domain logins where applicable.
WWW: https://www.samba.org/
===> The following configuration options are available for samba411-4.11.15_1:
ADS=on: Active Directory client(implies LDAP)
AD_DC=on: Active Directory Domain Controller
AESNI=on: Accelerated AES crypto functions(amd64 only)
CLUSTER=off: Clustering support
CUPS=off: CUPS printing system support
DEVELOPER=off: With developer framework(implies NTVFS)
DOCS=on: Build and/or install documentation
FAM=on: File Alteration Monitor
GPGME=off: GpgME support
LDAP=on: LDAP client
MANDOC=off: Build manpages from DOCBOOK templates
NTVFS=off: Build *DEPRECATED* NTVFS file server
PROFILE=on: Profiling data
QUOTAS=on: Disk quota support
SPOTLIGHT=off: Spotlight server-side search support
SYSLOG=on: Syslog logging support
UTMP=on: UTMP accounting
====> VFS modules
FRUIT=on: MacOSX and TimeMachine support
GLUSTERFS=off: GlusterFS support
====> GSSAPI Security API support: you have to select exactly one of them
GSSAPI_BUILTIN=on: GSSAPI support via bundled Heimdal
GSSAPI_MIT=off: GSSAPI support via security/krb5
====> Zero configuration networking: you have to select exactly one of them
ZEROCONF_NONE=off: Zeroconf support is absent
AVAHI=on: Zeroconf support via Avahi
MDNSRESPONDER=off: Zeroconf support via mDNSResponder
====> DNS frontend: you can only select none or one of them
NSUPDATE=off: Use samba NSUPDATE utility for AD DC
BIND911=off: Use Bind 9.11 as AD DC DNS server frontend
BIND916=off: Use Bind 9.16 as AD DC DNS server frontend
===> Use 'make config' to modify these settings
Remove expired ports:
2021-04-22 net/samba411: Security Support ends on 03 Dec 2020
2021-04-22 net-im/cordless: Unmaintained and dead upstream, uses the old Discord
API which notably has got users banned
2021-04-18 news/plor: listed as "Alpha-release" but last update in 2001;
unmaintained
2021-04-20 security/certificate-transparency: Broken for more than 6 months
net/samba411 net/samba412 net/samba413: Fix zero-sized VLAs
With recent versions of clang, samba could dump core shortly after
startup, terminating with either SIGILL or SIGSEGV.
Investigation showed that samba is using C99 variable length arrays
(VLAs), and in some cases the length of these arrays would become zero.
Since this is undefined behavior, various interesting things would
happen, often ending in segfaults.
Fix this by avoiding to use zero as the length for these VLA
declarations.
A similar patch was also sent upstream, and was accepted and included in
subsequent samba releases.
See also: https://bugzilla.samba.org/show_bug.cgi?id=14605
Reported by: Dries Michiels <driesm.michiels@gmail.com>
PR: 252157
MFH: 2021Q1
Security update for samba411, samba412 and samba413:
CVE-2020-14318 (Missing handle permissions check in SMB1/2/3 ChangeNotify)
CVE-2020-14323 (Unprivileged user can crash winbind)
CVE-2020-14383 (An authenticated user can crash the DCE/RPC DNS with easily
crafted records)
Security: CVE-2020-14318
CVE-2020-14323
CVE-2020-14383
