huh so what is this mt7921? wifi chipset or SoC?
PaulFertser has joined #openwrt-devel
aparcar[m]: fuzzing is ongoing project, you can take a look at libubox, cgi-io, mdnsd, ubus, ucert, uci projects it's in tests/fuzz
ianchi has joined #openwrt-devel
I've locally some wip in other projects, like for example odhcpd, but this needed a lot of refactoring (and maybe needs even more) so the user controlled and possibly malicious input (packet parsing) stuff could be used for fuzzing
such "noop" changes/refactoring introduce regressions, so I want to have a possibility to runtime test them first and thus I got stuck at this runtime testing preparation stage for about a year now :p
anyway, there is no magic involved, it's just a lot of manual work
and I've a plan to submit that into oss-fuzz as well, once I'm happy with it
currently we run the fuzzers via daily scheduled CI jobs on GitLab.com
but it's very limited testing, basically preventing already fixed regressions as the fuzzer runtime is limited to 5 minutes
ideally there should be some project dedicated to this, with status page for every project (CI, -Wextra, static analyzers, ubsan, valgrind, unit tests, fuzzing) and sort them by priority with network exposed services and shipped by default first
and document the workflow, thus make it possible for others to join the effort
Grommish, if some "standard" types are not picked up its sometimes because of source code flags and/or compiler settings ; some "portable" sources use POSIX_SOURCE or some other variants (some include libbsd ...) and afaik musl is more standard "conform"
plntyk: Is there a C/CXX flag I could add?
seems like a kludge that a meta-package has to have an empty /install rules section... but then we don't have a way of calling out meta-packages explicitly, so... maybe there's no better way for now?
well, not *entirely* empty. a single "\t:" rule...
speaking of firewall, when does it get refreshed next?
was just looking at his logs, sorted lines by nick, jow (and permutations) is the runaway leader over the last decade-ish (about 7.8%).
For the package folks. I'm making a Config.in file for options. If these options are set in ./configure as flags, do I have to do an ifeq($(CONFIG_xxx),y) to insert the --whatever in the CONFIGURE_ARGS?