Re: [PATCH] px5g-mbedtls (Was: px5g return value checking)

On Mon, Nov 7, 2022 at 7:19 AM Peter Naulls wrote: > > On 11/3/22 14:49, Peter Naulls wrote: > > > > Another one from our security scan: > > > > File: /usr/sbin/px5g > > Issue: RET NOT ASSIGNED in function 'FUN_000281b0' at address 0x281c0 while > > calling 'mbedtls_rsa_check_pub_priv' > > Issue:

[PATCH] px5g-mbedtls (Was: px5g return value checking)

On 11/3/22 14:49, Peter Naulls wrote: Another one from our security scan: File: /usr/sbin/px5g Issue: RET NOT ASSIGNED in function 'FUN_000281b0' at address 0x281c0 while calling 'mbedtls_rsa_check_pub_priv' Issue: RET NOT ASSIGNED in function 'FUN_000285e8' at address 0x285f8 while calling '

[PATCH] libtasn1: CVE-2021-46848

On 11/3/22 12:01, Etienne Champetier wrote: Hi Peter, Can you resend this as a proper patch ready to be applied ? Or as a PR on Github if this is easier for you ? Sorry, retry. I wasn't 100% sure of the filename setup for submitted patches. I've got a couple more to come. As per: https://nv

Re: [PATCH] ramips: fix Unifi 6 Lite boot failure with v5.15 kernels

Hi Bjorn, On 11/7/22 13:57, Bjørn Mork wrote: Jonas Gorski writes: On Sun, 6 Nov 2022 at 12:50, Bjørn Mork wrote: Jonas Gorski writes: An option is also to set a load address for the dtb in the FIT image, then U-Boot will relocate it before passing it to the kernel. Yes, that is worth t

Re: [PATCH] ramips: fix Unifi 6 Lite boot failure with v5.15 kernels

Jonas Gorski writes: > On Sun, 6 Nov 2022 at 12:50, Bjørn Mork wrote: >> Jonas Gorski writes: >> >> > An option is also to set a load address for the dtb in the FIT image, >> > then U-Boot will relocate it before passing it to the kernel. >> >> Yes, that is worth trying. I thought this would be

Re: [PATCH] ramips: fix Unifi 6 Lite boot failure with v5.15 kernels

On Sun, 6 Nov 2022 at 12:50, Bjørn Mork wrote: > > Jonas Gorski writes: > > > An option is also to set a load address for the dtb in the FIT image, > > then U-Boot will relocate it before passing it to the kernel. > > Yes, that is worth trying. I thought this would be part of the fdt > relocatio

Re: VLAN not working in 22.03 through netifd

On Sun, 2022-11-06 at 17:16 +, David Woodhouse wrote: > That worked, but *only* for VLAN2 which is in the original 'br-lan' > but *not* for VLAN3: > > bridge name bridge id STP enabled interfaces > tag 7fff.06bde9e2bd93 yes lan4 > br-lan6

Re: [RFC] dropping of $(AUTORELEASE) feature

Hi, > The AUTORELEASE has been a nice feature from the package PR maintenance > perspective. > > Earlier there was constant trouble with concurrent PRs for the same package > having the same PKG_RELEASE bump, or the maintainer doing a small change with > a bump while there was an open PR with the

Re: [RFC] dropping of $(AUTORELEASE) feature

Hi, yes, please kill it. The $(AUTORELEASE) option does not work for sources without Git history, it produces different results depending on the history, it causes package bumps for even trivial cosmetic fixes. It can also lead to situations where packages on different branches end up with the ex

Re: [RFC] dropping of $(AUTORELEASE) feature

Hannu Nyman writes: > The AUTORELEASE has been a nice feature from the package PR > maintenance perspective. > > Earlier there was constant trouble with concurrent PRs for the same > package having the same PKG_RELEASE bump, or the maintainer doing a > small change with a bump while there was an

Re: [RFC] dropping of $(AUTORELEASE) feature

On Mon, Nov 7, 2022 at 9:41 AM Josef Schlehofer wrote: > > > On 06. 11. 22 21:22, Hannu Nyman wrote: > > Paul Spooren kirjoitti 6.11.2022 klo 18.15: > >> While I initially thought that $(AUTORELEASE) would be a nice feature > >> to avoid the standard review comment “Please bump the PKG_RELEASE”, >