From mboxrd@z Thu Jan 1 00:00:00 1970 From: IPFire Nightly Builder To: nightly-builds@lists.ipfire.org Subject: [SUCCESS] Nightly Build of next (e698090) for aarch64 on arm64-01.dub.ipfire.org Date: Mon, 06 Apr 2020 18:10:59 +0000 Message-ID: <48wz9v6XMcz1yRY@arm64-01.dub.ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5445997526200639394==" List-Id: --===============5445997526200639394== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable https://nightly.ipfire.org/next/2020-04-06%2014%3A04%3A00%20%2B0000-e698090e/= aarch64 commit e698090e7f696923ff146b272b587a3eeca34c6c Author: Stefan Schantl Date: Fri Apr 3 16:25:01 2020 +0200 IDS: Dynamically generate and import the HTTP ports. =20 With this commit suricata reads the HTTP port declarations from a newly introduced external file (/var/ipfire/suricata/suricata-http-ports.yaml). =20 This file dynamically will be generated. HTTP ports always are the default port "80" and "81" for update Accelerator and HTTP access to the WUI. In case the Web-proxy is used, the configured proxy port and/or Tran= sparent Proxy port also will be declared as a HTTP port and written to that file. =20 In case one of the proxy ports will be changed, the HTTP port file will be re-generated and suricate restarted if launched. Also if an old backup with snort will be restored the convert script handles the generation of the HTTP ports file. =20 Finally the suricata-generate-http-ports-file as a tiny script which simply generates the http ports file and needs to be launched during the installation of a core update. (The script will no be required anymore, so it could be deleted afterwards.) =20 Fixes #12308. =20 Signed-off-by: Stefan Schantl Signed-off-by: Arne Fitzenreiter https://git.ipfire.org/?p=3Dipfire-2.x.git;a=3Dshortlog;h=3De698090e7f696923f= f146b272b587a3eeca34c6c --===============5445997526200639394==--