On Thu, Aug 6, 2020 at 6:13 PM Adrian Schmutzler
wrote:
>
> > I've tested 5.4 (a3ffeb413b to be precise) with an Asus RT-N56U
> > (rt3883) lightly, and all appears to be in order. It is a backup remote AP
> > with
> > light traffic. There is nothing unusual in the logs, and the single client
>
Hi
On Sat, Aug 1, 2020 at 10:54 AM wrote:
>
> Hi,
>
> with a 20.xx branch coming closer, we still have 3 of 6 ramips subtargets
> (rt288x, rt305x, rt3883) on kernel 4.14 by default (though 5.4 testing
> support is available in principle).
>
> I've recently tried to build those with 5.4 and buil
On Mon, May 25, 2020 at 5:06 AM Felix Fietkau wrote:
>
> On 2020-05-25 02:19, Eneas U de Queiroz wrote:
> > Individual packages may turn off MIPS16 ISA individually with
> > PKG_USE_MIPS16. However, they may link to a library compiled with
> > MIPS16. In such cases, the -minterlink-mips16 is nee
On Sat, Apr 11, 2020 at 7:23 PM Jo-Philipp Wich wrote:
>
> Hi Eneas,
>
> I am sorry but I had to completely revert the kconfig bump. It thoroughly
> broke the package repository builds since multiple days and the fatal
> recursive dependencies make it a no-go for master, at least as far as our
> b
It would be easier if I could reproduce the bug locally.
I would like to take a look at the failed 'Config-build.in' (haven't
seen this file ever), and 'tmp/.config-package.in'.
Meanwhile, I will try my luck with the SDK, which I don't do very often myself.
Do the phase1 bots have the feeds enab
Hi
On Sat, Apr 11, 2020 at 11:07 AM Hannu Nyman wrote:
>
> Looks like the recent kconfig changes broke the whole packages buildbot.
>
> (For some weird reason, the arc targets succeed, but all others fail
> miserably... )
>
>
> http://buildbot.openwrt.org/master/packages/grid
>
> http://buildbo
On Tue, Apr 7, 2020 at 5:19 AM Petr Štetiar wrote:
>
> Eneas U de Queiroz [2020-04-06 17:10:30]:
>
> Hi,
>
> > TLDR: You can't review this by only looking at the patches.
>
> Just tried to build[1] test it on x86/64 sunxi/a53 imx6 ipq40xx and it fails
> to build:
>
> make -s -C scripts/config co
On Wed, Feb 26, 2020 at 10:48 AM Paul Oranje wrote:
>
> Having read the whole conversation: an impressive piece of work.
>
> Could this helps with ipq806x ?
> On ipq806x qce isn't available on all SOCs (supposedly only on ipq8064) and
> therefore support has been removed from the kernel [1].
>
>
Hi
I have finished working on
https://github.com/openwrt/openwrt/pull/2518, fixing some bugs with
the crypto engine, and adding asm modules to crypto algorithms, since
the engine is not very fast when using "network-sized" (<1500-bytes)
requests.
Since it's been started a while back, it appears o
On Tue, Jan 7, 2020 at 6:42 PM Hauke Mehrtens wrote:
>
> On 1/7/20 9:09 PM, Eneas Queiroz wrote:
> > On Mon, Jan 6, 2020 at 1:59 PM Hauke Mehrtens wrote:
> >>
> >> I cherry-picked it, but WPA3 still does not work for me.
> >>
> >> Hauke
> >
On Mon, Jan 6, 2020 at 1:59 PM Hauke Mehrtens wrote:
>
> I cherry-picked it, but WPA3 still does not work for me.
>
> Hauke
TLDR: WPA3 support with wolfssl is still not ideal.
WPA3 success was reported to me here:
https://forum.openwrt.org/t/wpa3-wolfssl-fail-openssl-success/50161/7
Another use
On Wed, Jan 1, 2020 at 6:54 PM Hauke Mehrtens wrote:
> I will shift both releases (18.06.6 and 19.07.0 final) to Monday 6.
> January to get some security fixes in, please get your changes in till
> Saturday so we have some testing before.
>
>
I would suggest a cherry-pick from d5ede68f8b (wolfss
On Wed, Nov 27, 2019 at 10:28 AM Russell King - ARM Linux admin
wrote:
> The build system is just very painful for a new-comer to understand.
> I don't doubt that it does what you need it to, but trying to work
> out stuff from it is a nightmare unless you have some knowledge
> about how it is set
On Fri, Sep 27, 2019 at 8:05 AM W. Michael Petullo wrote:
>
> A daemon I wrote for OpenWrt depends on a running syslogd. I use
> syslog-ng, and I have noticed that its init script completes before the
> daemon begins to listen on /dev/log. This causes my daemon to terminate
> if it starts quickly
This is meant for 19.07, as it's already in master. I just now
realized it was missing from the subject line. Sorry about that.
Eneas
On Wed, Sep 25, 2019 at 2:03 PM Eneas U de Queiroz
wrote:
>
> This adds the CRYPTO_ALG_KERN_DRIVER_ONLY flag to Qualcomm crypto engine
> driver algorithms, so t
On Tue, Sep 24, 2019 at 7:07 PM Petr Štetiar wrote:
>
> Eneas Queiroz [2019-09-24 18:28:44]:
>
> > I've got your patch applied, and it still fails make menuconfig if I
> > start from scratch or after make -C scripts/config clean. I haven't
> > tried k
Sorry for the double reply, Peter, this did not make it to the list.
On Tue, Sep 24, 2019 at 5:42 PM Petr Štetiar wrote:
>
> Eneas Queiroz [2019-09-24 17:06:28]:
>
> Hi,
>
> > The problem is that when scripts/config/lxdialog/check-lxdialog.sh is run,
> > it will sti
This is still failing on gentoo. The problem is that when
scripts/config/lxdialog/check-lxdialog.sh is run, it will still use
the staging_dir/host/bin/pkg-config script without STAGING_PREFIX set.
See my suggestion below.
On Mon, Sep 23, 2019 at 4:39 AM Petr Štetiar wrote:
>
> On a recent Gentoo
On Mon, Sep 23, 2019 at 2:12 PM Rosen Penev wrote:
>
> On Mon, Sep 23, 2019 at 5:28 AM Eneas Queiroz wrote:
> >
> > On Fri, Sep 20, 2019 at 5:48 PM Eneas U de Queiroz
> > wrote:
> > >
> > > This adds the CRYPTO_ALG_KERN_DRIVER_ONLY flag to Qualcomm cryp
On Fri, Sep 20, 2019 at 5:48 PM Eneas U de Queiroz
wrote:
>
> This adds the CRYPTO_ALG_KERN_DRIVER_ONLY flag to Qualcomm crypto engine
> driver algorithms, so that openssl devcrypto can recognize them as
> hardware-accelerated.
>
> Signed-off-by: Eneas U de Queiroz
I noticed this was moved to ip
On Tue, Sep 17, 2019 at 10:52 AM Eneas U de Queiroz
wrote:
>
> This version fixes 3 low-severity vulnerabilities:
>
> - CVE-2019-1547: ECDSA remote timing attack
> - CVE-2019-1549: Fork Protection
> - CVE-2019-1563: Padding Oracle in PKCS7_dataDecode and
> CMS_decrypt_set1_pkey
>
I just realized now that my reply went to Hauke only, so I'm sending
it again to the mailing list, as it may be useful for more people.
On Fri, Sep 20, 2019 at 5:43 PM Hauke Mehrtens wrote:
>
> On 9/19/19 4:18 AM, Eneas U de Queiroz wrote:
> > WolfSSL added a wolfSSL_X509_check_host function to p
I forgot to mention it, but this is fix is for 19.07 only.
Eneas
Em seg, 8 de jul de 2019 às 11:20, Eneas U de Queiroz
escreveu:
>
> Commit 3167a57 missed it.
>
> Signed-off-by: Eneas U de Queiroz
>
> diff --git a/package/libs/wolfssl/Makefile b/package/libs/wolfssl/Makefile
> index 7aaa562539.
Can someone please cherry-pick this to 19.07:
2792daab5a wolfssl: update to 3.15.7, fix Makefile
This includes a fix for a medium-level potential cache attack with a
variant of Bleichenbacher’s attack. Patches were refreshed.
Increased FP_MAX_BITS to allow 4096-bit RSA keys.
Fixed poly1305 build
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 ---
Try
this:https://patch-diff.gith
25 matches
Mail list logo
