Ilya Shipitsin

> The invitation did go to spam, but I found it. > > Seems like coverity is complaining nearly every time we use warn() (or info(), fatal(), error(), etc.) because...

there's non zero probabilty that "ppp" [configures itself](https://github.com/ppp-project/ppp/blob/master/configure.ac#L14) to use plugins from pppoe folder. I ran steps from CI, in folder "pppd" I see: ``` ~/ppp/pppd$ grep -i pppoe Makefile...

coverity is trying to develop their software. not every time is successful. they deployed overflow checks in june 2024, those integer overflow checks now are just noise

I ran new scan to find out whether this commit https://github.com/ppp-project/ppp/commit/cb593953b52597e1d2b09c9056e1f4ab15462c7c is noticed by coverity in fact, it was

if that suites your situation, can you try 3.0-dev2 (released couple of days ago) ?

I'm trying current haproxy master using the following "[qemu in linux](https://github.com/vmactions)" actions: https://github.com/chipitsine/haproxy/actions/runs/7923059299/job/21631988366 (I'll play with mentioned defines in a week)

hopefully, we can enable monthly builds of solaris/netbsd/openbsd, it should not burn much electricity on running vm in vm

@OlegGavri , is it compliance requirement ? I've found that svacer is affiliated with Russian governmental IT activities https://svacer.ispras.ru/mediawiki/index.php?title=Svacer is there a requirement from some governmental org to pass svacer...

I wonder what is FIPS support status on HAProxy side. is it considered as first class citizen or ...