As of July 1st, 2024, FreeBSD 13.2 will reach end-of-life and will no longer be supported by the FreeBSD Security Team. Users of FreeBSD 13.2 are strongly encouraged to upgrade to a newer release as soon as possible. The currently supported branches and releases and their expected end-of-life dates are available at the article.
Link to previous parts are at the beginning of the article.
The Valuable News weekly series is dedicated to provide summary about news, articles and other interesting stuff mostly but not always related to the UNIX/BSD/Linux systems.
This guide will show you step by step how to setup FreeBSD based Samba server and serve shares with FreeIPA/IDM credentials.
See the video or read the transcript of interview with Beastie - the BSD Deamon mascot.
Results from the 2024 FreeBSD Community Survey Report, What is Computer Science? ~1967, Computation Poems, Old Info, but still good -- HOWTO: Set up and configure security/sshguard-pf, observium-freebsd-install, FreeBSD Tips and Tricks: Native Read-Only Root File System, OpenSSH introduces options to penalize undesirable behavior, and more.
When a new processor is released, how long would you expect it to take before your favorite operating system adds support for it? In the case of OpenBSD/arm64, the time lag can occasionally be measured in days if not hours. In a recent message to tech@, Patrick Wildt (patrick@) premiered the patch to add support for the Qualcomm Snapdragon Elite X processor the day after it was officially released.
This is the last bit of preparation for the upcoming 24.7 series reimplementing one-to-one NAT using MVC/API and a number of plumbing changes. IPv6 has also been improved with the dhcp6c client having received a number of new fixes and features.
C++14 and later supports size-aware deletion of heap objects, when the compiler is able to determine at compile time what the exact size of a particular object is. For this purpose, there are specific variants of "operator delete" that take an additional size_t argument. If such a variant is called, the size is passed through to the underlying allocator, which can optionally utilize this size for for more efficient deallocation. A recent change in libc++'s implementation of std::string has introduced a potential mismatch between the actual size allocated on the heap for the contained string, and the size that is passed to "operator delete" when the string is eventually destroyed.
The code designed to prevent lock order reversals between killpg(2) and fork(2) did not wait for lock availability before retrying to acquire a lock, which could result in a livelock causing very high system load.
Due to a bug in the library's configuration file parser, commented out configuration settings in /etc/resolv.conf were picked up by the LDNS resolver, potentially leading to malfunction and/or information leakage. This included, but was not limited to, the nameserver setting.
When writing data to a file on ZFS, the kernel may need to handle soft page faults that can occur when accessing user data. When doing so, in some cases ZFS needs to undo an earlier kernel buffer allocation. A bug in the handling of these cases causes this buffer to be leaked.