Uptime Kuma has recently released version 1.23.3, bringing important bug fixes and security updates to its server monitoring software.

One important note for users is that due to a security fix, all login sessions will be logged out after updating to this version. This is a necessary measure to ensure the security of the system.

If you are using any unofficial or third-party tools with Uptime Kuma, it is important to be aware that this update may introduce breaking changes. In such cases, it may be necessary to re-generate an authentication token to ensure compatibility.

The latest release includes several bug fixes that address various issues reported by the user community. These bug fixes include:

• Fixed an issue where notifications were not working if the configuration was too long. This improvement was contributed by @FJBlok.
• Enabled status page certificate expiry badge for all HTTP(s) monitors, thanks to @marvinruder.
• Fixed bugs related to the Kafka producer, with contributions from @mhkarimi1383.
• Addressed an issue where x-forwarded-host was not being utilized correctly. This fix was provided by @xuexb.
• Resolved a race condition issue in the status page editor that prevented some data from being saved when clicked too quickly. This fix was made possible by @chakflying.

In addition to bug fixes, version 1.23.3 also brings important security fixes. One notable fix addresses a persistent session tokens issue. Prior to this update, there was no way to revoke session tokens even if the password was changed. With this update, users can now revoke session tokens by changing their password. More information about this security fix can be found here.

This latest release of Uptime Kuma provides users with important bug fixes and security updates, ensuring a more reliable and secure server monitoring experience.

Debian 12.2 has been released, incorporating the latest security fixes and stable back-ports for Debian 12 Bookworm. This stable point release includes a new version of the Linux 6.1 kernel and the latest linux-firmware/microcode support.

One of the notable updates in Debian 12.2 is the inclusion of mitigations for the AMD Inception (SRSO) vulnerability, which was made public in August. Additionally, the release addresses the Intel Downfall vulnerability, also disclosed in August.

Furthermore, Debian 12.2 includes several other security fixes, enhancing overall system security. For a detailed list of package updates and security fixes, refer to the release announcement on Debian’s website.

Source: Phoronix.

Linux Containers has released Incus 0.1, the first formal release of their community fork of the LXD project. Incus was created after Canonical took control of LXD. Incus 0.1 is similar to the LXD 5.18 release but includes several changes and improvements. The project has dropped unused or problematic features from the LXD codebase and will now focus on backwards compatibility. Notable changes include renaming the project to Incus and replacing /dev/lxd with /dev/incus. More details and downloads can be found at LinuxContainers.org.

Source: Phoronix.

OpenZFS has launched release candidate 5 (rc5) of version v2.2.0.

The release includes several changes and updates, including improvements to ZIL (ZFS Intent Log), rpm fixes, enhancements to zfsconcepts, and updates to ARC (Adaptive Replacement Cache) headers. Additionally, there are compatibility updates for Linux and FreeBSD platforms.

Here are the supported platforms for this release:

• Linux: compatible with 3.10 - 6.5 kernels
• FreeBSD: compatible with releases starting from 12.2-RELEASE

The release candidate includes numerous bug fixes and enhancements to improve stability and performance. It is recommended for users who are interested in testing the latest features and providing feedback to the OpenZFS community.

To learn more and download the release candidate, visit the official OpenZFS GitHub page at https://github.com/openzfs/zfs/releases/tag/zfs-2.2.0-rc5.

Synapse, an open-source Matrix homeserver developed and maintained by the Matrix.org Foundation, has announced the release of its first release candidate (rc1) for v1.94.0. Synapse has been under development since 2014 and reached version 1.0.0 in 2019.

The release candidate, v1.94.0rc1, introduces several features, improvements, and documentation updates. Here is a summary of the key changes:

Features

• Inline rendering of plain, CSS, CSV, JSON, and common image formats in the browser when requested through the /download endpoint.
• Experimental support for MSC4028, which pushes all encrypted events to clients.
• Minor performance improvements when sending presence to federated servers.
• Minor performance improvement by caching server ACL checking.

Improved Documentation

• Developer documentation on gradual schema migrations with column alterations.
• Improved documentation of the user directory search algorithm.
• Fixed rendering of user admin API documentation related to deactivation.
• Updated documentation on message retention policies.
• Clarification note added to the federation_domain_whitelist config option.
• Improved legacy release notes.

Deprecations and Removals

• Removed Python version from /_synapse/admin/v1/server_version endpoint.

Internal Changes

• Avoid running CI steps when the checked files have not been changed.
• Improved type hints.
• Added support for pydantic v2 in addition to pydantic v1.
• CI now checks that PRs have been signed-off.
• Added missing license header.
• Improved comments in StateGroupBackgroundUpdateStore.
• Updated maturin configuration.
• Downgraded replication stream time out error log lines to warning.

Updates to locked dependencies

• Bumped actions/checkout from 3 to 4.
• Bumped cryptography from 41.0.3 to 41.0.4.
• Bumped various other dependencies such as dawidd6/action-download-artifact, docker/setup-buildx-action, gitpython, msgpack, phonenumbers, psycopg2, pydantic, regex, sentry-sdk, types-netaddr, and urllib3.

This release candidate of Synapse brings various new features, improvements, and documentation updates to the Matrix homeserver. Users and developers can now test and provide feedback on the release candidate to help ensure a stable and reliable final release of v1.94.0.

GL.iNet has released the Flint2 (also known as GL-MT6000), a new AX6000 router based on the MediaTek MT7986 (Filogic 830) ARM SoC. This router supports VPN speeds of up to 900 Mbps using WireGuard and 190 Mbps with OpenVPN. Compared to previous GL.iNet routers like the Spitz AX and the Beryl AX, which were based on the Filogic 820 (MT7981B) CPU with transfer rates of up to 300 Mbps using WireGuard, the Flint2 is expected to triple the VPN performance.

The GL.iNet Flint2 router comes with the following specifications:

• SoC – MediaTek MT7986 (Filogic 830) quad-core Arm Cortex-A53 processor @ 2.0 GHz with hardware acceleration engines for Wi-Fi offloading and networking
• System Memory – 1GB DDR4
• Storage – 8GB eMMC flash
• Networking:
  • 2x 2.5 Gbps Ethernet ports
  • 4x Gigabit Ethernet LAN ports
  • 802.11b/g/n/ac/ax WiFi 6 with 4x external Wi-Fi antennas
    • Up to 1,148 Mbps @ 2.4 GHz
    • Up to 4,804 Mbps @ 5 GHz
    • DFS (Dynamic Frequency Selection) support
  • VPN – OpenVPN server/client tested up to 190 Mbps, and WireGuard server/client tested up to 900 Mbps (tests over Ethernet in client mode)
• USB – 1x USB 3.0 Type-A port
• Dimensions – 233 x 137 x 57mm

The GL.iNet Flint2 router comes pre-installed with OpenWrt 23.05 (or a fork) with Linux 5.15 and the GL.Inet Admin Panel, which is common to all GL.iNet routers. It supports four different network modes: router, access point, extender, and WDS. The router also includes features such as AdGuard Home, parental controls, and Cloud remote management.

The significant improvement in WireGuard performance, tripling the previous model’s speed, is noteworthy. While the upgrade from a 1.3 GHz dual-core Arm Cortex-A53 CPU to a 2.0 GHz quad-core Cortex-A53 CPU partially explains the increase, the main reason is likely the switch from Linux 5.4 to Linux 5.15. The Filogic 830-based router benefits from in-kernel WireGuard support introduced in Linux 5.6. As a point of comparison, the first Flint router achieves speeds of up to 500 Mbps with WireGuard.

The Filogic 830 SoC used in the Flint2 is also found in other devices, such as the Banana Pi BPI-R3 and BPI-R3 Mini router SBCs.

Source: CNX Software – Embedded Systems News.