Re: [mod-security-packagers] ModSecurity 3.x (almost) enters Debian
Brought to you by:
victorhora,
zimmerletw
From: Felipe Z. <fe...@zi...> - 2018-10-19 13:51:35
|
Hi, Good to hear that we are having those packages :) that should increase even more the adoption of v3 :) Kudos!!!! Same as Ervin here, I am not able to reproduce the regression tests failures. Do you mind to share the configuration/compilation logs? Br., F. On Fri, Oct 19, 2018 at 10:14 AM Ervin Hegedüs <ai...@gm...> wrote: > Hi Alberto, > > On Fri, Oct 19, 2018 at 10:39:00AM +0200, Alberto Gonzalez Iniesta wrote: > > Hi, > > > > I'm happy to announce that the package for (lib)mod-security 3.x entered > > Debian unstable this week. But some issues arose in the testing suite > > with some/all of the architectures: > > > > - In most of them this test fails: > > > > ./regression_tests .././test/test-cases/regression/variable-ENV.json:1 > > :test-result: FAIL variable-ENV.json:Testing Variables :: ENV (2/3) > > > > - In some (i.e. s390) a bunch of ip matching rules tests fail [1] > > > > > > You may see all the build logs here: > > https://buildd.debian.org/status/package.php?p=modsecurity&suite=sid > > > > Some help with these issues would be really apreciated. > > I've grabbed your source, here are some info: > > $ cat /etc/debian_version > buster/sid > > Everything is up-to-date (I'm after an apt-get update, apt-get > dist-upgrade). > > apt-get source modsecurity > Reading package lists... Done > Need to get 2798 kB of source archives. > Get:1 http://cdn-fastly.deb.debian.org/debian sid/main modsecurity > 3.0.2-1 (dsc) [1967 B] > Get:2 http://cdn-fastly.deb.debian.org/debian sid/main modsecurity > 3.0.2-1 (tar) [2793 kB] > Get:3 http://cdn-fastly.deb.debian.org/debian sid/main modsecurity > 3.0.2-1 (diff) [2924 B] > Fetched 2798 kB in 1s (2651 kB/s) > dpkg-source: info: extracting modsecurity in modsecurity-3.0.2 > dpkg-source: info: unpacking modsecurity_3.0.2.orig.tar.gz > dpkg-source: info: unpacking modsecurity_3.0.2-1.debian.tar.xz > > cd modsecurity-3.0.2 > > debuild -us -uc > ... > make check-TESTS > make[3]: Entering directory '/home/airween/debian/modsecurity-3.0.2' > make[4]: Entering directory '/home/airween/debian/modsecurity-3.0.2' > ( 3/ 0/ 3): > test/test-cases/regression/action-ctl_request_body_access.json > ( 3/ 0/ 3): > test/test-cases/regression/action-ctl_request_body_processor.json > ... > ( 3/ 0/ 3): test/test-cases/regression/config-secremoterules.json > > ============================================================================ > Testsuite summary for modsecurity 3.0 > > ============================================================================ > # TOTAL: 4740 > # PASS: 4740 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 0 > # XPASS: 0 > # ERROR: 0 > ... > ... > Now running lintian modsecurity_3.0.2-1_amd64.changes ... > Finished running lintian. > > And that's it. > > > Check it by hand: > > cd test/ > ./regression_tests .././test/test-cases/regression/variable-ENV.json > ModSecurity 3.0.2 - tests > (options are not available -- missing GetOpt) > > # File Name Test Name > Passed? > --- --------- --------- > ------- > 1 variable-ENV.json Testing Variables > :: ENV (1/3) passed! > 2 variable-ENV.json Testing Variables > :: ENV (2/3) passed! > 3 variable-ENV.json Testing Variables > :: ENV (3/3) passed! > > Ran a total of: 3 regression tests - All tests passed. 0 skipped test(s). > 0 disabled test(s). > > > I've tried with pbuilder, here is the relevant part of the log: > > ( 3/ 0/ 3): test/test-cases/regression/variable-ENV.json > ... > ... > RUN: test/test-cases/regression/variable-ENV.json > ================================================= > > :test-result: PASS variable-ENV.json:Testing Variables :: ENV (1/3) > > ./regression_tests .././test/test-cases/regression/variable-ENV.json:1 > :test-result: PASS variable-ENV.json:Testing Variables :: ENV (2/3) > > ./regression_tests .././test/test-cases/regression/variable-ENV.json:2 > :test-result: PASS variable-ENV.json:Testing Variables :: ENV (3/3) > > ./regression_tests .././test/test-cases/regression/variable-ENV.json:3 > ... > > > (but there are another failed tests with pbuilder: > > UN: test/test-cases/regression/config-secremoterules.json > ========================================================== > > :test-result: FAIL config-secremoterules.json:Include remote rules > > ./regression_tests > .././test/test-cases/regression/config-secremoterules.json:1 > :test-result: FAIL config-secremoterules.json:Include remote rules - > failed download (Abort) > > ./regression_tests > .././test/test-cases/regression/config-secremoterules.json:2 > :test-result: PASS config-secremoterules.json:Include remote rules - > failed download (Warn) > > > this occured I guess that I'm behind proxy, and didn't pass > http_proxy env to pbuilder. > > > > ./regression_tests > .././test/test-cases/regression/operator-ipMatchFromFile.json:2 > :test-result: FAIL operator-ipMatchFromFile.json:Testing Operator :: > @ipMatchFromFile - https > > ./regression_tests > .././test/test-cases/regression/operator-ipMatchFromFile.json:3 > > also could occured by network problem) > > > I can't reproduce your issue on amd64 arch. > > > May be this can helps you, here is the output of ldd of compiled shared > object > which built in regular system (not with pbuilder) > > https://pastebin.com/svAjTek9 > > may be some library needs...? > > > regards, > > > a. > > > > _______________________________________________ > mod-security-packagers mailing list > mod...@li... > https://lists.sourceforge.net/lists/listinfo/mod-security-packagers > |