Gargoyle Forum

Ah, Broadcom. Unfortunately most likely the case yes.

Can you check your /etc/config/wireless looks ok? Expecting to see “sae” or “sae-mixed” for encryption and the “key” you set. Has wpa3 worked on previous builds for you before this change? Are you using the same SSID for both 2.4 and 5GHz? Might be worth forgetting the network as well if the auth me...

That apk change looks like it will be acceptable. I need to read it in much more detail.

I have patches for netfilter-match-modules you’ll want to compile against 25. I’ll try to send those through soon.

I think patching apk won't be _that_ bad.
And I also think it should be reasonably maintainable.

Probably does not work as we install mbedtls, not openssl. The CRL isn't private or special, I'd probably just throw it into an online CRL decoder to verify quickly. It's on my todo list to improve mbedtls-clu to decode CRLs, which is the missing piece in my mind to doing a full UI implementation (i...

I will find time to merge them upstream and compile, but I now have a backlog of changes to review first.
I had a large influx of changes to review in a single 48 hour window and more have followed.
It takes time.

What have you got so far? Happy to help out

If you want to let Claude have a go at it you can try. Prompt needs to be refined to keep it on track. My suggestion for context/promot: - gpkg is a Gargoyle specific fork of opkg - gpkg extended some features and customised returned data formats and attributes (e.g. JS format) to suit Gargoyle - gp...

Image metadata is written to the end of the compressed file. This is used during the sysupgrade process.

The decompression works fine, trailing garbage is ignored by all unzip programs written "well".

When you go to sysupgrade in the future do not unzip, just upload it as is.

I am not really that interested in taking it on sorry.
I don't have the bandwidth to review the change.

If I had to choose one, extend APK to suit Gargoyle.