From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: OpenWrt 22.03.2 second service release
Date: Mon, 17 Oct 2022 13:30:21 -0700 [thread overview]
Message-ID: <CAA93jw4KPoS5yYAT+sdNA_+przTXh9_hXC_spCeHCzMYXbxVkA@mail.gmail.com> (raw)
In-Reply-To: <6fc66699-7cef-2dce-889d-656cda8842a8@hauke-m.de>
it is so wonderful how fast openwrt can respond to a zero-day.
---------- Forwarded message ---------
From: Hauke Mehrtens <hauke@hauke-m.de>
Date: Mon, Oct 17, 2022 at 1:22 PM
Subject: OpenWrt 22.03.2 second service release
To: <openwrt-announce@lists.openwrt.org>, OpenWrt Development List
<openwrt-devel@lists.openwrt.org>
Hi,
The OpenWrt community is proud to announce the newest stable release of
the OpenWrt 22.03 stable version series. It fixes security issues,
improves device support, and brings a few bug fixes.
Download firmware images using the OpenWrt Firmware Selector:
* https://firmware-selector.openwrt.org/?version=22.03.2
Download firmware images directly from our download servers:
* https://downloads.openwrt.org/releases/22.03.2/targets/
Main changes between OpenWrt 22.03.1 and OpenWrt 22.03.2:
========================================================
Security fixes
==============
* mac80211/cfg80211: Security fixes for BSSID parsing
(CVE-2022-41674, CVE-2022-42719, CVE-2022-42720, CVE-2022-42721 and
CVE-2022-42722)
* See Security Advisory 2022-10-17-1
* https://openwrt.org/advisory/2022-10-17-1
Device support
==============
* Support for the following devices was added:
* ZyXEL NWA50AX / NWA55AXE (ramips)
* ramips/mediatek: backport NAND flash driver from master
* mpc85xx: p1010: make TP-Link WDR4900 v1 build again
Various fixes and improvements
==============================
* busybox: nslookup: Fix wrongly dropped DNS response on some platforms
Core components update
======================
* Update rpcd from 2022-08-24 to 2022-09-21
* Update ucode from 2022-08-29 to 2022-10-07
* Update firewall4 from 2022-09-01 to 2022-10-14
-----------------
Full release notes and upgrade instructions are available at
https://openwrt.org/releases/22.03/notes-22.03.2
In particular, make sure to read the regressions and known issues before
upgrading:
https://openwrt.org/releases/22.03/notes-22.03.2#known_issues
For a detailed list of all changes since 22.03.1, refer to
https://openwrt.org/releases/22.03/changelog-22.03.2
To download the 22.03.1 images, navigate to:
https://downloads.openwrt.org/releases/22.03.2/targets/
Use OpenWrt Firmware Selector to download:
https://firmware-selector.openwrt.org/?version=22.03.2
As always, a big thank you goes to all our active package maintainers,
testers, documenters and supporters.
Have fun!
The OpenWrt Community
---
To stay informed of new OpenWrt releases and security advisories, there
are new channels available:
* a low-volume mailing list for important announcements:
https://lists.openwrt.org/mailman/listinfo/openwrt-announce
* a dedicated "announcements" section in the forum:
https://forum.openwrt.org/c/announcements/14
* other announcement channels (such as RSS feeds) might be added in the
future, they will be listed at https://openwrt.org/contact
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
parent reply other threads:[~2022-10-17 20:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6fc66699-7cef-2dce-889d-656cda8842a8@hauke-m.de>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw4KPoS5yYAT+sdNA_+przTXh9_hXC_spCeHCzMYXbxVkA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox