public inbox for nightly-builds@lists.ipfire.org
 help / color / mirror / Atom feed
From: IPFire Nightly Builder <nightly-builds@ipfire.org>
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	[thread overview]
Message-ID: <48wz9v6XMcz1yRY@arm64-01.dub.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1578 bytes --]

https://nightly.ipfire.org/next/2020-04-06%2014%3A04%3A00%20%2B0000-e698090e/aarch64

commit e698090e7f696923ff146b272b587a3eeca34c6c
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date:   Fri Apr 3 16:25:01 2020 +0200

    IDS: Dynamically generate and import the HTTP ports.
    
    With this commit suricata reads the HTTP port declarations from a newly
    introduced external file
    (/var/ipfire/suricata/suricata-http-ports.yaml).
    
    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 Transparent
    Proxy port also will be declared as a HTTP port and written to that file.
    
    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.
    
    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.)
    
    Fixes #12308.
    
    Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=e698090e7f696923ff146b272b587a3eeca34c6c



                 reply	other threads:[~2020-04-06 18:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48wz9v6XMcz1yRY@arm64-01.dub.ipfire.org \
    --to=nightly-builds@ipfire.org \
    --cc=nightly-builds@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox