Mateusz Jończyk wrote on 06.04.23 14:18:
W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze:
Hi,
this paper is about CVE-2022-47522 which seems to be fixed in all
supported OpenWrt branches by commits that were pushed 7 days ago by
Felix Fietkau.
E.g. 4ae854d05568bc36a4df
Hi all,
Last night we tagged two new point releases for the 22 and 21 releases. I’m
traveling right now but will try to write the release notes later today.
Best,
Paul
> On 7. Apr 2023, at 18:31, openwrt-de...@matthias-larisch.de wrote:
>
>
>>
>> Mateusz Jończyk wrote on 06.04.23 14:18:
>>>
Mateusz Jończyk wrote on 06.04.23 14:18:
W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze:
Hi,
I was wondering whether you would like to delay the release until this is fixed
in mainline Linux.
Hi Mateusz,
this paper is about CVE-2022-47522 which seems to be fixed in al
W dniu 6.04.2023 o 20:57, Andreas Ziegler pisze:
>
> Mateusz Jończyk wrote on 06.04.23 14:18:
>> W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze:
>>> Hi,
>>>
>>> I would like to create a new OpenWrt 22.03 and 21.02 minor release in
>>> the next week.
>>>
>>> OpenWrt 21.02.6 wo
Mateusz Jończyk wrote on 06.04.23 14:18:
W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze:
Hi,
I would like to create a new OpenWrt 22.03 and 21.02 minor release in
the next week.
OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series.
Hello,
Last week,
W dniu 28.03.2023 o 00:54, hauke at hauke-m.de (Hauke Mehrtens) pisze:
> Hi,
>
> I would like to create a new OpenWrt 22.03 and 21.02 minor release in
> the next week.
>
> OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series.
Hello,
Last week, a vulnerability in some WiFi stack
On Tue, Mar 28, 2023 at 11:44 AM Paul Spooren wrote:
> >
> > How should simple github PRs that are intended be applied to both
> > /master and /openwrt-22.03 be handled?
>
> Feel free to open both at the same time to have the CI running, however be
> sure to mark the backport as “draft” and once
> On 28. Mar 2023, at 09:09, Joseph Mullally wrote:
>
>> If we should backport more changes please create a pull request on
>> github, send a patch with the 22.03 or 21.02 prefix to the mailing list
>> or send a mail with a link to the master commit we should backport as an
>> answer to this ma
> If we should backport more changes please create a pull request on
> github, send a patch with the 22.03 or 21.02 prefix to the mailing list
> or send a mail with a link to the master commit we should backport as an
> answer to this mail and I will have a look at the commit.
How should simple gi
Thanks for the info :)
On 3/28/23, Hauke Mehrtens wrote:
> Hi,
>
> I would like to create a new OpenWrt 22.03 and 21.02 minor release in
> the next week.
>
> OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series.
>
> On github the following pull requests are tagged for the releas
Hi Hauke,
May I have a little offtopic question about backporting?
I opened a pull request ("comgt: support Mikrotik R11e-LTE6 modem", [1])
where I move a file dependency from "comgt-ncm" to "comgt".
Are such a change allowed to be backported?
[1]: https://github.com/openwrt/openwrt/pull/1226
Hi,
I would like to create a new OpenWrt 22.03 and 21.02 minor release in
the next week.
OpenWrt 21.02.6 would be the final release of the OpenWrt 21.02 series.
On github the following pull requests are tagged for the releases:
https://github.com/openwrt/openwrt/pulls?q=is%3Apr+is%3Aopen+labe
12 matches
Mail list logo
