[continued from previous message]

This project aims to improve the support of Syzkaller on FreeBSD. Based on the existing WiFi fuzzer designed for Linux, we drafted a WiFi fuzzer for FreeBSD. We planned to use wtap(4), a virtual wifi driver for testing, in order to support WiFi fuzzing.

Some of the design details include:

• Introduce a new netlink command to wtap in order to realize frame
injection, which is essential for WiFi fuzzing.

• Initialize wtap devices in Syzkaller before WiFi fuzzing.

We are developing some prototypes and discussing the feasible design plan with some experts. There is not much progress yet. We hope to have more progress on this project in the next few months.

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Architectures

Updating platform-specific features and bringing in support for new hardware platforms.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Pinephone Pro Support

Links:
Repository on Codeberg URL: https://codeberg.org/Honeyguide/freebsd-pinephonepro

Contact: Toby Kurien <toby@tobykurien.com>

The project to port FreeBSD over to the Pinephone Pro is progressing. The aim of this project is to step by step support components of the Pinephone Pro in FreeBSD so that the device one day might be usable as a highly mobile FreeBSD device.

In this quarter:

• A driver for the RK818 power management IC was implemented, enabling the
device regulators.

• A driver for the real-time clock was also implemented, allowing the system
to keep time between reboots.

• A driver for the RK818 battery charger and battery monitor was written to
allow the battery to be charged via USB, and to retrieve some battery
information like voltage and charging status via sysctl.

• The code repository has been updated with scripts and documentation on how
to compile the custom kernel and device tree, and patch a FreeBSD
15-CURRENT image with them so that it boots on the Pinephone Pro.

The next steps are to enable UEFI-based framebuffer support to enable output to the screen, and to enable USB on-the-go functionality, which might allow for plugging in a USB keyboard and/or Ethernet. Porting the Linux driver for WiFi will also be looked into. Any developers wanting to assist are encouraged to get in touch. Additional feedback and testers are welcome.

Also see this thread on the FreeBSD Forum if you want to participate.

Sponsor: Honeyguide Group

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Cloud

Updating cloud-specific features and bringing in support for new cloud platforms.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD on Microsoft HyperV and Azure

Links:
Microsoft Azure article on FreeBSD wiki URL: https://wiki.freebsd.org/MicrosoftAzure
Microsoft HyperV article on FreeBSD wiki URL: https://wiki.freebsd.org/HyperV

Contact: Microsoft FreeBSD Integration Services Team <bsdic@microsoft.com> Contact: freebsd-cloud Mailing List
Contact: The FreeBSD Azure Release Engineering Team <releng-azure@FreeBSD.org> Contact: Wei Hu <whu@FreeBSD.org>, <weh@microsoft.com>
Contact: Souradeep Chakrabarti <schakrabarti@microsoft.com>
Contact: Colin Su <yuas@microsoft.com>
Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>

In this quarter, we have published the 14.2-RELEASE on Azure Marketplace.

Colin Su has presented at the FreeBSD 2024 Fall Summit about Azure DevOps Pipeline.

Souradeep Chakrabarti from Microsoft has added a feature to use hypercalls for TLB shootdown on Hyper-V and Azure.

Wei Hu root-caused an issue on missing CDROM device when booting FreeBSD on the latest Azure v6 VM SKU. V6 type only offers NVMe disks to guest OS. He also continues bug fixing for FreeBSD MANA NIC device.

Work in progress tasks:

• Automating the image publishing process and merging to src/release/.
(Li-Wen Hsu)

• Colin Su is testing adding FreeBSD support in Azure Pipelines

□ https://github.com/microsoft/azure-pipelines-agent/pull/3266

□ Building and publishing snapshot builds to Azure community gallery.

Open tasks:

• Update FreeBSD-related doc at Microsoft Learn

• Update sysutils/azure-agent to the latest version

• Upstream local modifications of Azure agent

• Port Linux Virtual Machine Extensions for Azure

Sponsor: Microsoft for people in Microsoft, and for resources for the rest Sponsor: The FreeBSD Foundation for everything else

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

OpenStack on FreeBSD

Links:
OpenStack URL: https://www.openstack.org/
OpenStack on FreeBSD URL: https://github.com/openstack-on-freebsd

Contact: Chih-Hsin Chang <starbops@hey.com>
Contact: Li-Wen Hsu <lwhsu@FreeBSD.org>

The OpenStack on FreeBSD project aims to merge the capabilities of the OpenStack cloud infrastructure with the robust features of FreeBSD. Our objective is to harness FreeBSD’s unique features while ensuring compatibility
with OpenStack’s operations.

In the fourth quarter, our primary goal was to finalize the tasks promised under milestone 1 by establishing a new environment for a demonstrable Proof of Concept (POC) site. However, the simultaneous aim to set up another deployment based on FreeBSD Jail within the same environment led us to spend considerable time on network design and tuning. Fortunately, we successfully established external network connectivity for guest VMs by the end of this period. The remaining challenge now is to enable guest VMs to automatically acquire IP addresses through cloud-init.

On another note, we attempted to obtain the domain XML of VMs from the Linux-based OpenStack to compare with the XML used for bhyve VMs. These domain XMLs are utilized by Libvirt, defining each virtual machine’s configuration and
operational parameters. Comparing the differences between the two will aid in developing the "bhyve serial console over TCP" work.

In the first quarter of the upcoming year, we will continue to conclude the tasks related to milestone 1 of our project. Additionally, we will persist in developing FreeBSD Ports for OpenStack components, further integrating and enhancing the system’s capabilities.

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Containers and FreeBSD: Cloud Native Buildpacks

Contact: Robert Gogolok <gogolok@gmail.com>

Cloud Native Buildpacks (CNBs) transform application source code into container images. Those images can run on any cloud. With buildpacks, organizations can concentrate the knowledge of container build best practices within a specialized team, instead of having application developers across the organization individually maintain their own Dockerfiles.

A few weeks ago, I’ve started to look into FreeBSD support for buildpacks. My goal is to have working versions of the tools lifecycle and pack in the next few months.

There were previous attempts to bring support for FreeBSD to buildpacks, for example to lifecycle:

• Add support for FreeBSD #1087

• Add FreeBSD Support #1271

After looking into those changes, I’ve decided to first introduce some general
cleanup steps to keep the required changes for FreeBSD small.

This resulted in the following changes that were successfully integrated:

• Remove obsolete // +build lines #1431

• Use unix build constraint #1432

• Support FreeBSD build phase #1439

With these steps, it is now possible to compile lifecycle under FreeBSD.

The next steps are:

• Provide missing FreeBSD functionality to lifecycle.

• Further investigate FreeBSD as a build target in lifecycle.

• Investigate and get the tool pack to compile and run under FreeBSD.

• Provide lifecycle and/or pack via FreeBSD ports.

• Investigate the idea of FreeBSD buildpacks for some popular languages,
similar to paketo buildpacks.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD on EC2

Links:
EC2 Boot performance over time URL: https://www.daemonology.net/freebsd-ec2-boot-performance/

Contact: Colin Percival <cperciva@FreeBSD.org>

FreeBSD is available on both amd64 (Intel and AMD) and arm64 (Graviton) EC2 instances.

In the past quarter, first boot performance of ZFS AMIs has been significantly improved, e.g. from about 22 seconds to about 11 seconds for 15.0 "base" AMIs on amd64. Graphs of boot performance over time are now being generated and published automatically; typical times are around 9-12 seconds for "base" and "small" AMIs and 14-18 seconds for "cloud-init" AMIs.

On Graviton systems, the EC2 "shutdown" and "reboot" operations now work as intended (starting with FreeBSD 14.2). On Graviton systems, adding new devices (e.g. EBS volumes) while the system is running now works in HEAD and support is expected to be merged in time for FreeBSD 14.3.

Sponsor: Amazon
Sponsor: https://www.patreon.com/cperciva

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Documentation

Noteworthy changes in the documentation tree, manual pages, or new external books/documents.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Documentation Engineering Team

Link: FreeBSD Documentation Project URL: https://www.freebsd.org/docproj/
Link: FreeBSD Documentation Project Primer for New Contributors URL: https://docs.freebsd.org/en/books/fdp-primer/
Link: Documentation Engineering Team URL: https://www.freebsd.org/administration/#t-doceng

Contact: FreeBSD Doceng Team <doceng@FreeBSD.org>

The doceng@ team is a body to handle some of the meta-project issues associated with the FreeBSD Documentation Project; for more information, see FreeBSD Doceng Team Charter.

Document changes

• Handbook:

□ Add warning about custom kernel configurations.

□ Mention Rocky Linux 9 userland.

□ Add notes to VMWare related setup guide.

• Committer’s guide: Document "Discussed with" Improve "Fixes:" metadata.

• Porter’s Handbook: Document new TCL_ variables.

• Website: Remove Turkish links.

• Documentation repository:

□ Added OpenBSD 7.6 manual pages.

□ Updated Debian 11/12 manpages.

FreeBSD Translations on Weblate

Link: Translate FreeBSD on Weblate URL: https://wiki.freebsd.org/Doc/Translation/Weblateurl
Link: FreeBSD Weblate Instance URL: https://translate-dev.freebsd.org/url

Q3 2024 Status

• 18 team languages

• 215 registered users

1 new translator joined Weblate:

• Sean Markham (ES)

Languages

• Chinese (Simplified) (zh-cn) (progress: 14%)

• Chinese (Traditional) (zh-tw) (progress: 11%)

• Dutch (nl) (progress: 1%)

• French (fr) (progress: 1%)

• German (de) (progress: 1%)

• Greek (el) (progress: 1%)

• Indonesian (id) (progress: 1%)

• Italian (it) (progress: 11%)

• Korean (ko) (progress: 30%)

• Norwegian (nb-no) (progress: 1%)

• Persian (fa-ir) (progress: 6%)

• Polish (progress: 2%)

• Portuguese (progress: 0%)

• Portuguese (pt-br) (progress: 31%)

• Sinhala (progress: 1%)

• Spanish (es) (progress: 39%)

• Spanish (Chile) (progress: 0%)

• Turkish (tr) (progress: 5%)

We want to thank everyone who contributed, translating, or reviewing documents.

And please, help promote this effort on your local user group; we always need more volunteers.

Packages maintained by DocEng

During this quarter the following work was done in packages maintained by doceng@:

• www/gohugo: update to 0.140.2

• misc/freebsd-doc-ja: fix build

Open issues

There is 1 open PR in Bugzilla assigned to doceng@:

• 276923 www/gohugo link error under poudriere

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Ports

Changes affecting the Ports Collection, whether sweeping changes that touch most of the tree, or individual ports themselves.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Ports Collection Accessibility - Colors Low Vision

Link:
Project wiki page URL: https://wiki.freebsd.org/portconfig

Contact: FreeBSD Accessibility mailing list <freebsd-accessibility@FreeBSD.org> Contact: Alfonso Sabato Siciliano <asiciliano@FreeBSD.org>

FreeBSD provides the Ports Collection to give users and administrators a simple way to install applications. The collection provides tens of thousands of ports; port configuration is a key feature. It is possible to configure a port before the building and installation. The command "make config" uses a text user interface (TUI) to set up port options interactively.

Recently low vision users (mainly with cataracts) have requested new features to easily change the colors of the TUI. Several features have been implemented to allow changing colors, for example: a new environment variable to set the UI to black and white, or the ability to set colors by reading a configuration file at runtime. All features have been described in portconfig(1) since version 0.6.2.

To note, blind users can refer to PortOptsCLI - Ports Collection Accessibility,
Status Report Third Quarter 2023 to use the Ports Collection.

Tips and new ideas are welcome. If possible, send reports to the FreeBSD Accessibility mailing list, to share and to track discussions in a public place.

Sponsored by: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Containers and FreeBSD: AppJail, Director, OCI and more

Links:
AppJail on GitHub URL: https://github.com/DtxdF/AppJail
Director on GitHub URL: https://github.com/DtxdF/Director
LittleJet on GitHub URL: https://github.com/DtxdF/LittleJet
Reproduce on GitHub URL: https://github.com/DtxdF/reproduce

Contact: Jesús Daniel Colmenares Oviedo <DtxdF@disroot.org>

AppJail is an open-source BSD-3 licensed framework entirely written in POSIX shell and C to create isolated, portable and easy to deploy environments using FreeBSD jails that behaves like an application.

Director is a tool for running multi-jail environments on AppJail using a simple YAML specification. A Director file is used to define how one or more jails that make up your application are configured. Once you have a Director file, you can create and start your application with a single command: appjail-director up.

LittleJet is an open source, easy-to-use orchestrator for managing, deploying, scaling and interconnecting FreeBSD jails anywhere in the world.

Their goals are to simplify life for sysadmins and developers by providing a unified interface that automates the jail workflow by combining the base FreeBSD tools.

AppJail and all its meta-projects extensively follow The Ephemeral Concept which helps update/upgrade jails more easily as they become disposable. I have used this extensively to deploy my jails with services since this concept was implemented in AppJail.

Although there have been great people working on OCI for a long time, this month the featured topic is OCI, and the advances related to this technology in FreeBSD make it possible to implement it in AppJail. The latest release adds more useful features, improves on existing things and implements OCI.

I’m continually adding more Makejails, a simple text file that automates the deployment of services in jails. There is an organization on GitHub that I call The Centralized Repository if you want to make a contribution. The last improvement was to implement BuildBot as the CI/CD of AppJail images, so any change made to a repository that is tracked by BuildBot will generate a new task to build and deploy an image to the mirrors. And if mirrors are not an option, appjail-reproduce can be used to build images using your own resources.

Sponsor: https://www.patreon.com/appjail

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Improving Common Lisp Infrastructure in FreeBSD Ports

Contact: Joe Mingrone <jrm@FreeBSD.org>

Common Lisp (CL) is a general-purpose, multi-paradigm programming language first conceived in the early 1980s. Although it predates many modern programming languages, it remains a viable option for many different projects. One contemporary example is Grammarly, a widely used grammar engine reportedly implemented in CL and capable of processing over a thousand sentences per second.

The FreeBSD ports tree has provided CL support for many years. The initial work was contributed by Henrik Motakef in 2003, and then enhanced and maintained by Jimmy Olgeni. The infrastructure facilitated building and installing CL libraries using ASDF so that multiple CL implementations could load compiled object code files (fasl) at run-time without conflicts.

However, many issues crept in over the years. Support dwindled to only one CL implementation, SBCL, and users encountered longstanding bugs such as conflicting ASDF versions and write errors when loading libraries outside the ports tree. Also, managing dependencies was cumbersome because most infrastructure code was included as part of the devel/cl-asdf port.

A long overdue update of the FreeBSD CL infrastructure was completed this quarter. The primary outcome is that users can, once again, easily and reliably work with CL on FreeBSD. For example, installing and loading the popular Alexandria library under SBCL requires only a few simple steps.

% pkg install cl-alexandria-sbcl
% sbcl
* (asdf:load-system :alexandria)

Similar steps can be used to load libraries for the other two newly supported implementations: CCL, and CLISP. Most users will likely prefer to work with the fasl ports, although there is no obligation to do so. Because ASDF is now configured to fall back to its default caching mechanism of writing fasl to a cache under ${HOME}, users can also install CL source ports without the associated fasl port or load CL sources from outside of the ports tree.

Other highlights of the update include:

• decoupling ASDF initialization from devel/cl-asdf by creating a dedicated
port: devel/freebsd-cl-asdf-init

• creating USES=cl

• adding and updating various CL library ports for the three supported
implementations

• updating and modernizing lang/ccl and lang/clisp

For details, refer to these commit logs:

• 4c954c1522cbf4d05013caaf40c36458d82f1480

• f6a75a8f9bf20dbf1e9a4d5bc171d58f595c1ec1

• 1d7c75a5cde6792b3872340edeaf8f278add291a

• 148251b431b8d972623bb3adaa5a71355f47ac26

• 7f68336ed19be61027dfb7b461aacd056733eba4

The tentative plan is to add support for ECL after an ASDF output translation issue is solved and to create ports for other CL libraries. Feedback, testing, and contributions are welcome.

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

FreeBSD Erlang Ecosystem Ports update

Links:
FreeBSD Erlang wiki URL: https://wiki.freebsd.org/Erlang
Erlang/OTP language URL: https://erlang.org/
Elixir language URL: https://elixir-lang.org/
Gleam language URL: https://gleam.run/

Contact: FreeBSD Erlang mailing list <erlang@FreeBSD.org>

The Erlang runtime system, commonly known as the BEAM, provides a runtime that is used by a number of programming languages and applications in the FreeBSD ports collection.

In the final update for 2024, the Erlang ecosystem team has been busy:

• Regular updates to all Erlang/OTP releases, to stay current

• Elixir 1.18.1, Gleam 1.6.3, and RabbitMQ updates

Users of RabbitMQ need to update each quarter to avoid being stuck on an unsupported release of Erlang/OTP + RabbitMQ, without a supported migration path.

Note that as the upstream Erlang OTP team only commit to supporting the two latest major releases, more and more point updates are arriving for OTP26-27, but not for the older Erlang runtime releases, which are now unlikely to get security and bug fixes.

The Erlang team will be updating the default Erlang runtime to OTP26, to lang/ erlang, along with the usual dependencies and tooling.

Additional testing and community contributions are welcome; please reach out on the mailing list, especially if you are able to help testing of specific port updates.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Improve OpenJDK on FreeBSD

Links:
Project description URL: https://freebsdfoundation.org/project/ improving-openjdk-on-freebsd/

Contact: Harald Eilertsen <haraldei-fbsd@anduin.net>

The aim of this project is to improve support for Java in FreeBSD, by working with the upstream OpenJDK community, as well as the FreeBSD community in getting the changes and additions needed for fully supporting FreeBSD accepted upstream.

As this is a new project, there is not much to report yet, but here’s what has
been achieved so far:

• The Java Test Regression harness (jtreg) now builds and runs on FreeBSD,
and the process of upstreaming the changes has started.

• OpenJDK 23 builds and runs on FreeBSD, and work on adding it to the ports
collection has started; this is still considered experimental.
https://reviews.freebsd.org/D48194

• Work on porting the next OpenJDK (version 24) has started.
https://github.com/snake66/jdk/tree/jdk24-freebsd

Sponsor: The FreeBSD Foundation

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Xfce on FreeBSD

Links:
Xfce 4.20 Upstream Release Announcement URL: https://xfce.org/about/news/?post=1734220800
Xfce meta-port on FreshPorts URL: https://www.freshports.org/x11-wm/xfce4

Contact: Xfce team <xfce@FreeBSD.org>
Contact: Guido Falsi <madpilot@FreeBSD.org>

The FreeBSD Xfce team (xfce@) works to ensure the Xfce desktop environment is maintained and fully functional on FreeBSD.

This quarter the Xfce team members are pleased to welcome Xfce 4.20 to the FreeBSD ports tree!

This new release adds many stability improvements and some new functionality.

Upstream work for this release was focused on getting the code base ready for Wayland support.

This release brings experimental Wayland support, although not all components have been migrated, so it may not work for you.

For further details, refer to the Xfce 4.20 Upstream Release Announcement.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

LXQt on FreeBSD

Links:
LXQt Project URL: https://lxqt-project.org/
LXQt Project GitHub URL: https://github.com/lxqt

Contact: LXQt Team <lxqt@FreeBSD.org>

LXQt is an advanced, easy-to-use, and fast desktop environment based on Qt technologies. It has been tailored for users who value simplicity, speed, and an intuitive interface. Unlike most desktop environments, LXQt also works fine with less powerful machines.

During this quarter, the x11-wm/lxqt metaport was updated to 2.1.0. This update adds initial Wayland support to the LXQt desktop. You can read some release highlights here.

Anyone interested in helping with the project is welcome.

Current version: 2.1.0

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

GCC on FreeBSD

Links:
GCC Project URL: https://gcc.gnu.org/
GCC 11 release series URL: https://gcc.gnu.org/gcc-11/
GCC 12 release series URL: https://gcc.gnu.org/gcc-12/
GCC 13 release series URL: https://gcc.gnu.org/gcc-13/
GCC 14 release series URL: https://gcc.gnu.org/gcc-14/

Contact: Lorenzo Salvadore <salvadore@FreeBSD.org>

The exp-run to update GCC default version from 13 to 14 is getting forward. As usual, thanks to everyone involved.

If you maintain any of the affected ports or want to give a hand preparing and testing some patches, you can consider trying adding -fpermissive to CFLAGS in affected ports as a temporary solution: GCC 14 has transformed some warnings into errors, which is the cause of many of the failed builds. The -fpermissive flag switches those errors back to warnings. However, it is preferable that upstream updates its code to remove those warnings completely so that -fpermissive is not necessary, possibly with FreeBSD ports maintainers support. If the code is not maintained upstream anymore, the time might have come to deprecate the port.

Work has been done on some bugs too, mainly upstream:

• https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117210 has been fixed: a
recent change in the FreeBSD headers caused a regression in the GCC 15
development version;

• https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115008 has been fixed: this
was an issue with posix_fallocate failing on FreeBSD on a ZFS filesystem;

• an attempt to fix bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282797 specific to aarch64
for -devel ports has failed. If you are able to give a hand on this, it
would be very much appreciated.

Thanks to everyone who has helped with these issues.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Tor-Browser

Links:
Tor Project Homepage URL: https://www.torproject.org/
GitLab Repository URL: https://gitlab.torproject.org/tpo/applications/ tor-browser

Contact: Martin Filla <freebsd@sysctl.cz>

Since the last report, significant progress has been made in building and packaging Tor Browser for FreeBSD. Additionally, the Tor Browser version has been updated to 14.0.3, which is now available from the Tor Browser download page and also from our distribution directory.

This update includes important security updates to Firefox, ensuring that users benefit from enhanced security and privacy features. Expanding FreeBSD compatibility remains a priority to provide seamless and native privacy solutions for the platform.

What is new: Tor Browser version 14.0.3 includes:

• Rebase to Firefox 128.5.0esr.

• Backporting of security fixes from Firefox 133.

• Platform-specific updates such as disabling Microsoft SSO on macOS and
updating GeckoView for Android.

• Updated Go to version 1.22.9 in the build system.

Help Needed: To move forward, assistance is required in the following areas:

Code Review: Ensure patches meet the required coding and security standards. Testing: Volunteers are needed to test Tor Browser 14.0.3 on FreeBSD to identify edge cases. Bug Fixing: Developers familiar with FreeBSD and Firefox’s
codebase are encouraged to resolve known issues.

Feedback: If you find a bug or have suggestions for improving this release, please let us know through the GitLab Repository or the provided contact email.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Greenbone Vulnerability Management Community Edition

Links:
Greenbone URL: https://www.greenbone.net/en/
Greenbone GitHub URL: https://github.com/greenbone/

Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>

The Greenbone Community Edition (GVM) covers the actual source code of the Greenbone Vulnerability Management software stack, which is also known as OpenVAS scanner, a security feed with more than 160.000 vulnerability tests, a vulnerability management application, and much more.

During this quarter, security/gvm metaport was updated to 24.1.2. This update includes the following:

• databases/pg-gvm: Updated to 22.6.6

• security/gsa: Updated to 24.1.0 (Only amd64 and aarch64)

• security/gsad: Updated to 24.1.0

• security/openvas: Updated to 23.14.0

• security/gvmd: Updated to 24.1.2

• security/gvm-libs: Updated to 22.15.0

• security/py-notus-scanner: Updated to 22.6.5

• security/py-greenbone-feed-sync: Updated to 24.9.0

• security/py-ospd-openvas: Bump PORTREVISION

• security/py-gvm-tools: Updated to 24.12.1

• security/py-python-gvm: Updated to 24.12.0

A quick GVM jail installation to test it can be done using AppJail, makejail, or https://github.com/AppJail-makejails/greenbone-openvas.

Anyone interested in helping with the project or interested in aarch64 device donation for testing is welcome.

Current version: 24.1.2

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Wazuh on FreeBSD

Links:
Wazuh URL: https://www.wazuh.com/

Contact: José Alonso Cárdenas Márquez <acm@FreeBSD.org>

Wazuh is a free and open source platform used for threat prevention, detection, and response. It is capable of protecting workloads across on-premises, virtualized, containerized, and cloud-based environments.

Wazuh solution consists of an endpoint security agent, deployed to the monitored systems, and a management server, which collects and analyzes data

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)