Re: [RFC] 21.02.1 backports
Hi all, We evaluated the status this morning/evening and decided I favor of the Wolfssl bump to 4.8.1. I’ll push those changes later today. The actual tagging will happen Tuesday, images are excepted some 36 hours later. Regarding backports of specific devices, this means extra review time which should be used on the many many open PRs on master branch. I’d therefore kindly ask you to wait for the next release. Best, Paul > On 20. Oct 2021, at 13:01, Paul Spooren wrote: > > Hi all, > > Hauke an me plan to tag 21.02.1 this Friday. > > Motivation is the recent breakage (and fix) of HTTPS secured by Let's Encrypt > certificates. > More information is available in the commit message[0] of the fix. > > Please post your backport requests here so we can determine what's possible > to include in the next point release. > > Sunshine, > Paul > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [RFC] 21.02.1 backports
On 10/21/21 1:01 AM, Paul Spooren wrote: Hi all, Hauke an me plan to tag 21.02.1 this Friday. Motivation is the recent breakage (and fix) of HTTPS secured by Let's Encrypt certificates. More information is available in the commit message[0] of the fix. Please post your backport requests here so we can determine what's possible to include in the next point release. Sunshine, Paul Hi, Wolfssl has some known security problems, see here: https://www.wolfssl.com/docs/security-vulnerabilities/ I think they are not really relevant for us. OpenWrt master uses version 3.8.1 and OpenWrt 21.02 uses version 3.7.0, should we upgrade the version used in OpenWrt 21.02 too? Here is already a patch: https://patchwork.ozlabs.org/project/openwrt/list/?series=262295 Hauke ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [RFC] 21.02.1 backports
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Please back port https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=c829bc1f2c3c47e230905864f2f5f8c759f88ce6 which adds two additional very common Netgear switches to the realtek target. Thank you, Ray > On Oct 20, 2021, at 7:01 PM, Paul Spooren wrote: > > Hi all, > > Hauke an me plan to tag 21.02.1 this Friday. > > Motivation is the recent breakage (and fix) of HTTPS secured by Let's Encrypt > certificates. > More information is available in the commit message[0] of the fix. > > Please post your backport requests here so we can determine what's possible > to include in the next point release. > > Sunshine, > Paul > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel signature.asc Description: Message signed with OpenPGP --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[RFC] 21.02.1 backports
Hi all, Hauke an me plan to tag 21.02.1 this Friday. Motivation is the recent breakage (and fix) of HTTPS secured by Let's Encrypt certificates. More information is available in the commit message[0] of the fix. Please post your backport requests here so we can determine what's possible to include in the next point release. Sunshine, Paul ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
