Full Changelog: v4.0.0-beta.473...v4.0.0-beta.474
This version includes multiple breaking changes. If you are upgrading from v0.15.x and below, please read the upgrading documentation for more information on how to upgrade from previous versions.
Log inzxcvbn algorithmMX, TXT, CNAME, SRV, CAA and TLSA records (#463 #1017 #1419 #2438 #1370 #1406 #1371)TLSA records when ACME certificates change (#1664)SIG(0) support (#856)smtp, imap and memory directory backends.aws-lc for cryptographic operations instead of ring.rustls-platform-verifier for TLS certificate verification instead of webpki (#247).inMailboxOtherThan query logic.hasAttachment search field (#2778)8000 bytesRIGHTS capability (#2762)ACL SET permission override.304 NOT_MODIFIED on If-None-MatchPUT requests if they are equal to the existing ones.id sorteable.204 CORS preflight responses
VIENNA, Austria – April 20, 2026 – Enterprise software developer Proxmox Server Solutions (henceforth "Proxmox") and Kasm Technologies, a leader in zero-trust cloud workspaces, today announced a strategic solution partnership. The collaboration expands the Proxmox ecosystem with a secure, web-native workspace streaming layer for Proxmox VE. This integration enables organizations to deliver virtual desktops, application streaming, and remote browser isolation through any modern browser – on any device and from any location.
Built on the foundation of Proxmox Virtual Environment, Kasm Workspaces adds a modern workspace delivery layer that allows IT and security teams to provision, manage, and isolate workloads across Windows, Linux, and macOS from a unified stack. Kasm’s containerized, zero-trust approach ensures that end-users never interact directly with sensitive data or endpoints, helping organizations reduce risk while simplifying secure remote access.
The Proxmox and Kasm integration provides a DevOps-enabled alternative to legacy VDI environments. The combined solution reduces operational overhead, eliminates proprietary licensing constraints, and delivers a verifiable security architecture that can scale from small deployments to global enterprise rollouts.
Short Quote Kasm Technologies:
“Great technology partnerships are built on shared principles, and Kasm Technologies and Proxmox are united by a common belief: organizations of all sizes deserve infrastructure that works for them,” said Justin Travis, CEO of Kasm Technologies. “Together, we offer a full-stack VDI solution, from the hypervisor layer to the end-user experience, built on the reliability and rapid innovation that Proxmox’s open-source ecosystem is known for delivering.”
Short Quote Proxmox:
“At Proxmox, we believe open-source infrastructure should give organizations more freedom, not more complexity,” said Tim Marx, COO of Proxmox Server Solutions. “Kasm extends Proxmox Virtual Environment with a modern, browser-based workspace experience that aligns with the needs of today’s IT and security teams. This partnership gives customers a flexible and secure path to deliver virtual desktops and applications without the constraints of legacy VDI platforms.”
Kasm Workspaces on Proxmox Virtual Environment is available immediately. For more information, please visit https://kasm.com/alliance-partnership/proxmox
###
About Kasm Technologies
Kasm Technologies is a leading provider of cloud workspaces, delivering zero-trust browser isolation, Desktop-as-a-Service, and application streaming through its open-source, web-native container streaming platform. Founded by cybersecurity experts with decades of experience defending U.S. federal and Department of Defense programs, Kasm enables organizations to securely deliver digital workspaces to any device, any network, anywhere in the world. Kasm Technologies is headquartered in McLean, Virginia. Learn more at https://www.kasm.com
About Proxmox Server Solutions
Proxmox provides powerful and user-friendly open-source server software. Enterprises of all sizes and industries use the Proxmox solutions to deploy efficient and simplified IT infrastructures, minimize total cost of ownership, and avoid vendor lock-in. Proxmox also offers commercial support, training services, and an extensive partner ecosystem to ensure business continuity for its customers. Proxmox Server Solutions GmbH was established in 2005 and is headquartered in Vienna, Austria. To learn more visit https://www.proxmox.com
Media contact: Michael Hiess, Proxmox Server Solutions GmbH, marketing@proxmox.com
nginx-1.30.0 stable version has been released, incorporating new features and bug fixes from the 1.29.x mainline branch — including Early Hints, HTTP/2 to backend and Encrypted ClientHello, sticky sessions support for upstreams, Multipath TCP support, the default proxy HTTP version set to HTTP/1.1 with keep-alive enabled, and more.
/tcp, /udp, /sctp and IP-bound mappings. (#9503, fixes #9501, #9504)phpseclib/phpseclib to 3.0.51. (#9500)axios to 1.15.0 for development dependencies. (#9515)axios to 1.15.0 in coolify-realtime. (#9516)Full Changelog: v4.0.0-beta.472...v4.0.0-beta.473
The Asterisk Development Team would like to announce
the release of asterisk-23.3.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/23.3.0
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 23.3.0
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
The Asterisk Development Team would like to announce
the release of asterisk-22.9.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/22.9.0
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 22.9.0
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
The Asterisk Development Team would like to announce
the release of asterisk-20.19.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/20.19.0
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 20.19.0
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
/status.php (#9470)Full Changelog: v4.0.0-beta.471...v4.0.0-beta.472
Full Changelog: v4.0.0-beta.470...v4.0.0-beta.471
nginx-1.29.8 mainline version has been released.
The Asterisk Development Team would like to announce
release candidate 2 of asterisk-23.3.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/23.3.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 23.3.0-rc2
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: nappsoft
Date: 2026-04-02
When the res_cdrel_custom modules is reloaded and the config has not been changed asterisk should not free the old config. Otherwise the connection to the database will be closed and no new connection will be opened.
Resolves: #1852
Author: George Joseph
Date: 2026-03-31
Several issues are resolved:
Internally, floats were used for timestamp values but this could result
in wrapping so they've been changed to doubles.
Historically, the default CEL eventtime format is <seconds>.<microseconds>
with <microseconds> always being 6 digits. This should have continued to be
the case but res_cdrel_custom wasn't checking the dateformat setting in
cel.conf and was defaulting to %F %T. res_cdrel_custom now gets the default
date format from cel.conf, which will be whatever the dateformat parameter
is set to or <seconds>.<microseconds> if not set.
The timeval field formatter for both CDR and CEL wasn't handling custom
strftime format strings correctly. This is now fixed so you should be able
to specifiy custom strftime format strings for the CEL eventtime and CDR
start, answer and end fields. For example: eventtime(%FT%T%z).
Resolves: #1844
Resolves: #1845
The Asterisk Development Team would like to announce
release candidate 2 of asterisk-22.9.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/22.9.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 22.9.0-rc2
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: nappsoft
Date: 2026-04-02
When the res_cdrel_custom modules is reloaded and the config has not been changed asterisk should not free the old config. Otherwise the connection to the database will be closed and no new connection will be opened.
Resolves: #1852
Author: George Joseph
Date: 2026-03-31
Several issues are resolved:
Internally, floats were used for timestamp values but this could result
in wrapping so they've been changed to doubles.
Historically, the default CEL eventtime format is <seconds>.<microseconds>
with <microseconds> always being 6 digits. This should have continued to be
the case but res_cdrel_custom wasn't checking the dateformat setting in
cel.conf and was defaulting to %F %T. res_cdrel_custom now gets the default
date format from cel.conf, which will be whatever the dateformat parameter
is set to or <seconds>.<microseconds> if not set.
The timeval field formatter for both CDR and CEL wasn't handling custom
strftime format strings correctly. This is now fixed so you should be able
to specifiy custom strftime format strings for the CEL eventtime and CDR
start, answer and end fields. For example: eventtime(%FT%T%z).
Resolves: #1844
Resolves: #1845
The Asterisk Development Team would like to announce
release candidate 2 of asterisk-20.19.0.
The release artifacts are available for immediate download at
https://github.com/asterisk/asterisk/releases/tag/20.19.0-rc2
and
https://downloads.asterisk.org/pub/telephony/asterisk
Repository: https://github.com/asterisk/asterisk
Tag: 20.19.0-rc2
This release resolves issues reported by the community
and would have not been possible without your participation.
Thank You!
Author: nappsoft
Date: 2026-04-02
When the res_cdrel_custom modules is reloaded and the config has not been changed asterisk should not free the old config. Otherwise the connection to the database will be closed and no new connection will be opened.
Resolves: #1852
Author: George Joseph
Date: 2026-03-31
Several issues are resolved:
Internally, floats were used for timestamp values but this could result
in wrapping so they've been changed to doubles.
Historically, the default CEL eventtime format is <seconds>.<microseconds>
with <microseconds> always being 6 digits. This should have continued to be
the case but res_cdrel_custom wasn't checking the dateformat setting in
cel.conf and was defaulting to %F %T. res_cdrel_custom now gets the default
date format from cel.conf, which will be whatever the dateformat parameter
is set to or <seconds>.<microseconds> if not set.
The timeval field formatter for both CDR and CEL wasn't handling custom
strftime format strings correctly. This is now fixed so you should be able
to specifiy custom strftime format strings for the CEL eventtime and CDR
start, answer and end fields. For example: eventtime(%FT%T%z).
Resolves: #1844
Resolves: #1845
