bsdweekly.com

BSD Weekly is a free, once-weekly email round-up of BSD news and articles. Its content is organized into four sections—Releases, BSDSec, News, and Tutorials—and each issue mixes version announcements, security notices, community news, and how-to material. If you follow more than one BSD project and want a single weekly digest instead of monitoring each project's mailing lists and sites separately, this format is designed for that.

Releases

This section covers new versions across the BSD family. A single issue can include announcements for multiple projects, so you see OpenBSD, FreeBSD, and NetBSD release news side by side.

Coverage goes beyond the version number. For example, the Issue 301 entry for OpenBSD 8.0 describes:

• Multi-processor support for up to 64 guest VCPUs in vmd
• DRM graphics updated to Linux 6.18.53 with Intel Arc support
• Boot-time random relinking for httpd and smtpd
• amd64 kernel virtual address space expanded to 512G
• Hibernate support on arm64
• sparc64 switched to the LLVM toolchain
• Updates across the installer, pf firewall, and hardware drivers

That level of detail lets you judge whether an upgrade matters for your hardware or workload before you read the full release notes.

BSDSec

BSDSec collects security advisories and errata notices, which is often the most time-sensitive part of the newsletter. Entries typically name the affected versions and say how to get fixes.

Examples from Issue 301:

The practical value here is triage: you can scan one section and immediately see whether any advisory touches software you run, then follow the stated fix path (syspatch, freebsd-update, pkg, or a source patch).

News

The News section rounds up community and project developments that aren't releases or security notices. Issue 301, for instance, highlights NetBSD's stated AI-free stance alongside the release and advisory items. This is where policy positions, project announcements, and broader ecosystem stories tend to appear.

Tutorials

Tutorials points to how-to and instructional content from around the BSD community. Rather than publishing original guides, the newsletter surfaces tutorials published elsewhere, so it works as a curated reading list for people learning or deepening BSD skills.

How the Sections Fit Together

The four sections map to four different reader needs:

• Releases — decide whether and when to upgrade
• BSDSec — decide whether you need to patch now
• News — stay aware of project direction and community happenings
• Tutorials — find material for learning or solving a specific task

Because everything arrives in one weekly email, the newsletter suits administrators and enthusiasts who want broad coverage of the BSD landscape without subscribing to every project's separate announcement channels. Each issue is numbered and dated (Issue 301 is dated October 21, 2026), which makes it easy to check whether you've missed a week.

BSD Weekly is a free, once-weekly email newsletter that rounds up BSD news and articles in a single issue. It is aimed at people who want one consolidated digest of what is happening across the BSD family — releases, security advisories, news, and tutorials — rather than tracking many separate sources. Each issue is numbered and dated, so you can follow it as a running publication (the sample issue shown is Issue 301, published October 21, 2026).

What each issue covers

The newsletter organizes content into recurring sections. In the sample issue, the headings are Releases, BSDSec, News, and Tutorials.

How to use it

1. Subscribe by email — the newsletter is distributed as a weekly email, which is the primary delivery format described on the site.
2. Read by section — if you administer systems, start with BSDSec to see whether any advisory affects your versions; if you are evaluating upgrades, check Releases.
3. Follow issue numbers — issues are numbered sequentially (e.g., Issue 301), which makes it easy to reference or catch up on a specific week.

Who it is for

BSD Weekly suits system administrators, developers, and enthusiasts who run OpenBSD, FreeBSD, NetBSD, or related systems and want a periodic summary instead of monitoring each project's announcement channels. Because security items include affected versions and patch paths (for example, syspatch on OpenBSD or freebsd-update/pkg on FreeBSD), it can serve as a lightweight prompt to check whether your systems need updating — though you should always confirm details against the original advisory before acting.

Limitations to keep in mind

• It is a round-up, not a primary source: release notes and advisories are summarized, so verify specifics at the originating project.
• Content is weekly, so urgent security news may reach you with a delay of up to a week.
• The site describes the newsletter as free; no pricing or account requirements beyond email subscription are indicated in the available material.

BSD Weekly's security section, labeled BSDSec, summarizes BSD security advisories and errata notices in the same issue-by-issue format as the rest of the newsletter. Based on the published Issue 301 (October 21, 2026), the section covers OpenBSD errata, FreeBSD security advisories (SA) and errata notices (EN), the affected versions, and how patches are delivered. Each item is a short digest rather than the full advisory, so it is a way to spot what needs attention and then follow the link to the primary source.

What appears in the BSDSec section

The section mixes several distinct types of security communication, each with its own naming convention:

The distinction matters: SAs describe vulnerabilities that may be exploitable, while ENs cover defects such as timer overflows or data exposure that may not be framed as an attack vector. BSD Weekly lists both, so readers see correctness fixes alongside security patches.

How much detail each entry carries

Entries are compact but consistently include the pieces needed to triage:

• Affected versions. The OpenBSD errata item names OpenBSD 7.8, 7.9, and 8.0. The bhyve advisory names FreeBSD 14.4, 14.5, 15.0, and 15.1. The tcp_rack advisory is scoped to FreeBSD 15.1.
• Impact in one or two sentences. For example, the sound(4) advisory describes a TOCTOU race between buffer resizing and mmap that can let an unprivileged local user trigger a kernel use-after-free and potentially escalate privileges. The bhyve item describes vulnerabilities in device models (xHCI, HDA audio, framebuffer) that could let a malicious guest crash the bhyve process or execute code in the host userspace context.
• Patch path. The OpenBSD item notes binary updates via syspatch on amd64, arm64, and i386. The tcp_rack item notes updates via pkg, freebsd-update, or source patch.
• Scope caveats. The tcp_rack entry states that systems not using tcp_rack.ko are unaffected — the kind of qualifier that saves readers an unnecessary upgrade.

Kernel and driver vulnerabilities are a recurring theme

The Issue 301 sample shows the section regularly covering low-level components rather than only userland services:

• A kernel heap out-of-bounds write in the tcp_rack module, caused by a 16-bit allocation counter wrapping to zero (~512 KB write), potentially causing a panic.
• A TCP timer overflow in FreeBSD 15.1 and 14.4 that can make timers fire late or not at all, leaving connections stuck and consuming resources.
• A hastd(8) errata covering three issues, including uninitialized padding in nvpair that exposes configuration data in metadata, and a hang during primary-to-secondary transition that leaves HAST in degraded mode.
• OpenBSD errata spanning ppp, isakmpd, NSD, the X11 server, IPsec crypto, and a video driver.

This is useful if you administer systems where kernel modules, storage replication, or virtualization device models are in scope — the newsletter surfaces these even when they are not the headline release news.

What the section does not do

BSD Weekly is a round-up, so the BSDSec entries are summaries. They give you the advisory identifier, the affected versions, a plain-language impact statement, and the patch mechanism, but not the full technical analysis, CVSS scoring, or workaround detail that the original advisory may contain. For anything matching your environment, treat the entry as a pointer and read the source advisory before deciding on an upgrade window.

The newsletter is described as a free, once-weekly e-mail round-up of BSD news and articles, and the security section follows that cadence — you get a weekly digest of what was published, not real-time alerts. If you need immediate notification of advisories, subscribe to the vendor security lists directly and use BSD Weekly to keep the broader picture, including releases and tutorials, in one place.

BSD Weekly is a free, once-weekly English email newsletter that rounds up BSD news and articles. You can receive it by email subscription, and its issue-based format means each edition reads as a dated digest of releases, security notices, news, and tutorials. The site describes itself as a "free BSD e-mail newsletter," so the primary access path is the email list rather than a paywall or account system.

What BSD Weekly Provides

Each issue is organized into recurring sections. Based on the published issue content, the structure includes:

Issue 301, published October 21, 2026, illustrates the format: it covers the OpenBSD 8.0 release, several FreeBSD security advisories (sound, bhyve, tcp_rack), FreeBSD errata notices, and a NetBSD policy stance. This is a round-up model — the newsletter points to source material rather than replacing it.

Subscribing by Email

The newsletter is delivered by email on a weekly cadence. To subscribe:

1. Go to bsdweekly.com.
2. Locate the email sign-up form on the site.
3. Enter your email address and confirm the subscription.
4. Expect one issue per week; check your spam folder if the first issue does not arrive.

The site does not publish pricing details beyond describing the newsletter as free, and no login or account requirement is indicated in the available material. If a confirmation email is part of the sign-up flow, complete it to activate delivery.

Reading Issues Without Subscribing

Because BSD Weekly is issue-based, individual editions are identifiable by number and date (for example, "Issue 301, Published October 21, 2026"). This makes it possible to:

• Browse the site for published issue content and section headings.
• Search by issue number or date when you need a specific week's coverage.
• Follow linked sources — advisories, release notes, and tutorials — directly from an issue.

If you only need security information, the BSDSec section is the most efficient entry point; if you are tracking a specific release, the Releases section and the linked project announcements are more authoritative than the summary.

Deciding Whether It Fits Your Needs

BSD Weekly suits readers who want a single weekly digest across OpenBSD, FreeBSD, and NetBSD rather than monitoring each project separately. It is less suitable if you need real-time security alerts — advisories appear in the next issue, so subscribing directly to project security lists is better for immediate patching decisions. For hands-on learning, the Tutorials section is a starting point, but the linked original articles carry the full detail.