similar to: [Announce] Samba 4.9.3, 4.8.7 and 4.7.12 Security Releases Available

======================================================== "The whole point of getting things done is knowing what to leave undone." Oswald Chambers ======================================================== Release Announcements --------------------- Major bug fixes include: ------------------------ o dns: Fix CNAME loop prevention using counter regression (bug

======================================================== "The whole point of getting things done is knowing what to leave undone." Oswald Chambers ======================================================== Release Announcements --------------------- Major bug fixes include: ------------------------ o dns: Fix CNAME loop prevention using counter regression (bug

======================================================== "Fall forward!" Denzel Washington ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include: ------------------------ o dns: Fix CNAME loop prevention using counter regression (bug

======================================================== "Fall forward!" Denzel Washington ======================================================== Release Announcements --------------------- This is the latest stable release of the Samba 4.8 release series. Major bug fixes include: ------------------------ o dns: Fix CNAME loop prevention using counter regression (bug

I have seen a ton of messages on the list in the archives in reference to this but have not been able to find an answer to it. I will try to give as much info as possible so forgive me if this messages turns out to be long. Running FreeBSD 4.10 Samba 3.0.7 IBM e305 Server P4 2.0ghz 1gig of ECC Memory Boot Drive 40gig IDE Data Drive 250gig 8meg cache IDE 2 built in Gigabit Controllers

Release Announcements --------------------- These are a security releases in order to address the following defects: o CVE-2019-3870 (World writable files in Samba AD DC private/ dir) o CVE-2019-3880 (Save registry file outside share as unprivileged user) ======= Details ======= o CVE-2019-3870: During the provision of a new Active Directory DC, some files in the private/ directory

Release Announcements --------------------- These are a security releases in order to address the following defects: o CVE-2019-3870 (World writable files in Samba AD DC private/ dir) o CVE-2019-3880 (Save registry file outside share as unprivileged user) ======= Details ======= o CVE-2019-3870: During the provision of a new Active Directory DC, some files in the private/ directory

Hai,   There was an update on the samba packages. A few ctdb bugs where detected and fixed in these packages. The bug was reported here: https://bugzilla.samba.org/show_bug.cgi?id=13696 My change logs for this one, no big changes.  samba (2:4.9.3+nmu-1.1~deb9) stretch; urgency=medium  .    * resync debian default from Debian samba (2:4.9.2+dfsg-2)      - removed the CVE patches, already in

On Sun, 17 Feb 2019 18:26:21 +0100 Andrea Venturoli via samba <samba at lists.samba.org> wrote: > Hello. > > On several FreeBSD 11.2/amd64 servers, I've got a jail dedicated to > running Samba as an AD DC. > > Some days ago I upgraded one of them from 4.8.7 to 4.8.9 and suddenly > everything stopped working. > Since it was a production box, I immediately

This sounds familiar... I suggest you try without the interface names and only ipnumbers. Test 1) interfaces = 10.1.2.34/24 127.0.0.1 bind interfaces only = yes nbt client socket address = 127.0.0.1 Try again. In addition to test 1, Test 2. > ntlm auth=YES Remove that from the smb.conf then try again. At least for this test remove it. After a web search I found the solution

On Mon, 18 Feb 2019 09:13:45 +0100 Andrea Venturoli <ml at netfence.it> wrote: > On 2/17/19 8:18 PM, Rowland Penny via samba wrote: > > > Possible things to check: > > Is the ip for vlan1 10.1.2.34 ? > > Sure. > It's the only IP vlan1 has inside the jail; it's shown as an alias on > the base host. > > > > > Try just setting

Hai,   The Debian Stretch packages for samba 4.8.7 are now available for amd64 and i386.   ----------- THE REPO SETUP --------------- 1) Choose http or https for you apt, both work, for https you need to : apt-get install apt-transport-https   2) Import my public key wget -O - http://apt.van-belle.nl/louis-van-belle.gpg-key.asc | apt-key add -   3) (optional) setup a header line for the repo

Hello. On several FreeBSD 11.2/amd64 servers, I've got a jail dedicated to running Samba as an AD DC. Some days ago I upgraded one of them from 4.8.7 to 4.8.9 and suddenly everything stopped working. Since it was a production box, I immediately restored the whole jail from a backup, with no chance to better investigate. Today, with more time, I tried on another server and again I run

Hi, Currently, we have at my job a Samba 4 AD DC with 2 DC are running over Samba 4.1.11 version. I know both servers are out date. I want to update this version to the latest version (4.9.3), but I'm not confident about the process to do it. I've read on wiki.samba.org that is recommended read all release notes to version x.x.0 and all release notes the latest version you pretend update

Join new DC (from virtual machine) https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory (or 2. from 2 vm!) with bind/dhcp/.. Then demote old DC https://wiki.samba.org/index.php/Demoting_a_Samba_AD_DC and install (clean) 4.9.3, then join it again, demote vm,.. 01.12.2018 0:40, Igor Sousa via samba пишет: > I've tried use samba-tool domain backup, but the

Hai Julien, Uh... Samba 4.9.3 for Ubuntu Bionic (18.04) are now available for amd64 Only Was posted yesterday. you need more cofee... ;-) Here you go, the repo line. echo "deb http://apt.van-belle.nl/debian/ bionic-samba49 main contrib non-free" | sudo tee -a /etc/apt/sources.list.d/van-belle.list So have fun. Greetz, Louis > -----Oorspronkelijk bericht----- > Van:

Im wondering this also. Why are you using wheezy for samba AD.. You need to fix all needed depends first before you can even thing compiling samba. A few snaps out your attempt to build. Checking for program xsltproc : not found Checking for system cmocka (>=1.1.1) : not found Checking for

Hai, ? The Ubuntu Bionic (18.04) packages for samba 4.9.3 are now available for amd64 Only　 ? ----------- THE REPO SETUP --------------- 1) Choose http or https for you apt, both work, for https you need to : apt-get install apt-transport-https ? 2) Import my public key wget -O - http://apt.van-belle.nl/louis-van-belle.gpg-key.asc | apt-key add - ? 3) (optional) setup a header line for the repo

On 2/17/19 8:18 PM, Rowland Penny via samba wrote: > Possible things to check: > Is the ip for vlan1 10.1.2.34 ? Sure. It's the only IP vlan1 has inside the jail; it's shown as an alias on the base host. > Try just setting 'vlan1' You mean change "interfaces=vlan1 10.1.2.34/24" to just "interfaces=vlan1"? It doesn't change anything (still

On Mon, Dec 03, 2018 at 07:33:22PM +0100, Peter Eriksson via samba wrote: > Hmm… > > I see that there is a patch in the bugzilla page for that bug. I guess I could try that one… :-) > > I notice in the patch that there is a lot of talk about SMB2 - we use SMB3 mostly now. But perhaps there is some code sharing? Or perhaps SMB2 is used when talking to the AD servers? Or the few