Samba versions in ports and updating to newer version

[fre...@vanderzwan.org]

Hi
I am currently using samba419 from packages but when I ran pkg upgrade I got a message I should go to a newer version.
If I run pkg search I get the following versions, all with the same description:

$ pkg search samba4
samba416-4.16.11_12 Free SMB/CIFS and AD/DC server and client for Unix
samba419-4.19.9_13 Free SMB/CIFS and AD/DC server and client for Unix
samba420-4.20.8_2 Free SMB/CIFS and AD/DC server and client for Unix
samba422-4.22.10_1 Free SMB/CIFS and AD/DC server and client for Unix
samba423-4.23.8_1 Free SMB/CIFS and AD/DC server and client for Unix

In /usr/ports/UPDATING I see no relevant remarks about samba.
Can I just do pkg remove samba419 followed by pkg install samba423 ?
Or are there issues to expect ? And where can I find documentation of those issues ?

Cheers,
Paul

[Marco Moock]

Am 29.07.26 um 19:57 schrieb fre...@vanderzwan.org:

> In /usr/ports/UPDATING I see no relevant remarks about samba.
> Can I just do pkg remove samba419 followed by pkg install samba423 ?
> Or are there issues to expect ? And where can I find documentation of those issues ?

Maybe configuration has changed, you should read the release notes for
Samba. Then removing the old one and installing the new one is fine.
Do a backup of you old config first, so you can revert if needed.

--
Gruß
Marco

Junk-Mail bitte an tras...@stinkedores.dorfdsl.de

[fre...@vanderzwan.org]

> On 29 Jul 2026, at 20:00, Marco Moock <m...@dorfdsl.de> wrote:
>
> Am 29.07.26 um 19:57 schrieb fre...@vanderzwan.org:
>> In /usr/ports/UPDATING I see no relevant remarks about samba.
>> Can I just do pkg remove samba419 followed by pkg install samba423 ?
>> Or are there issues to expect ? And where can I find documentation of those issues ?
>
> Maybe configuration has changed, you should read the release notes for Samba. Then removing the old one and installing the new one is fine.
> Do a backup of you old config first, so you can revert if needed.
>

I run samba in a jail and the jails are snapshotted using sanoid every hour so rolling back is easy.
But for the changes it seems it's just reading the release notes for 4.20.0, 4.21.0, 4.22.0 and 4.23.8 and trying to figure out what is relevant for FreeBSD in general and my config in particular ?

Cheers,
Paul

[Marco Moock]

Am 29.07.26 um 20:07 schrieb fre...@vanderzwan.org:

> I run samba in a jail and the jails are snapshotted using sanoid every hour so rolling back is easy.
> But for the changes it seems it's just reading the release notes for 4.20.0, 4.21.0, 4.22.0 and 4.23.8 and trying to figure out what is relevant for FreeBSD in general and my config in particular ?

If you have a jail anyway, try the new version and if it does not work,
revert back to the old.
It is normally no issue to upgrade to a new Samba version.

Certain distributions just ship the new version.

[Frank Leonhardt]

Background info on Samba right now that might be relevant here...

https://www.samba.org/samba/security/CVE-2026-6949.html
https://www.samba.org/samba/security/CVE-2026-58216.html
https://www.samba.org/samba/security/CVE-2026-58221.html
https://www.samba.org/samba/security/CVE-2026-58222.html
https://www.samba.org/samba/security/CVE-2026-58224.html

At least two of these look to be potentially very serious (as a minimum
they can crash Samba on demand). Of the packages you mentioned above,
only 4.22.10 is the on fixed list. 4.23 needs to be .11+ and 4.24 (not
listed) needs to be .5+

Shout out to Nicola Mingotti for bringing this to my attention.

Regards, Frank.

[Andrea Venturoli]

On 7/29/26 20:07, fre...@vanderzwan.org wrote:

>>> Can I just do pkg remove samba419 followed by pkg install samba423 ?

Most of the times it works, but Samba is so vast, with hundreds of
configuration tweaks, that it's impossible to tell without knowing your
setup, your config, your network...

>>> Or are there issues to expect ? And where can I find documentation of those issues ?

At the very least you should read the release notes. There are very few
FreeBSD specific items.

>> Maybe configuration has changed, you should read the release notes for Samba. Then removing the old one and installing the new one is fine.

If you do, don't remember to run testparm, after the upgrade and before
starting Samba, and check the logs just after you start it.

>> Do a backup of you old config first, so you can revert if needed.
>>
>
> I run samba in a jail and the jails are snapshotted using sanoid every hour so rolling back is easy.

This is 99% true.
Alas, Samba is a network software, so it also interacts with other
machines and in some edge-cases just rolling back a single one might not
work.



P.S.
Some people say 4.16 is the last version that works/has been fully
tested on FreeBSD.
I personally only use 4.22 and 4.23 without any trouble.
I hope others will move on, so that more testing is done.



bye
av.

[fre...@vanderzwan.org]

Hi
My Samba server has very limited use, TimeMachine for 2 Mac and some filesharing on my local LAN.
So I removed samba419 and installed samba423, which seems to work fine, except for for some logging about Apple metadata.
Removed some vfs_fruit settings to go back to defaults and the logs are quiet now.

Cheers.
Paul

[Andrea Venturoli]

On 7/30/26 11:59, fre...@vanderzwan.org wrote:

> My Samba server has very limited use, TimeMachine for 2 Mac and some filesharing on my local LAN.
> So I removed samba419 and installed samba423, which seems to work fine

Good!

> except for for some logging about Apple metadata.
> Removed some vfs_fruit settings to go back to defaults and the logs are quiet now.

Strangely I saw something along this line when I upgraded to 4.22.
Upgrading again to 4.23 got rid of those messages.
Then again, our setups are almost surely different.

bye
av.