public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] show IDS rule names correctly in WebUI log
Date: Tue, 21 Nov 2017 12:06:09 +0000	[thread overview]
Message-ID: <1511265969.4838.563.camel@ipfire.org> (raw)
In-Reply-To: <20171120191314.4b55e2b5.peter.mueller@link38.eu>

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

Hi,

the bug ID is good, but it didn't have a precise explanation either.

I just wanted this on the record so that we know what this patch was supposed to
be doing.

Yes, please send again.

Best,
-Michael

On Mon, 2017-11-20 at 19:13 +0100, Peter Müller wrote:
> Hello Michael,
> 
> Emerging Threats changed some snort signature IDs to 5 digits
> a while, which were not displayed in the WebUI since "([0-9]{1,4})"
> did not match on it.
> 
> This patch adjusts the regular expression so they are displayed
> correctly now.
> 
> Should I send in a second version with this description? Thought
> the bug ID would be enough...
> 
> Best regards, 
> Peter Müller
> 
> > Hello,
> > 
> > can you explain what this patch is supposed to change?
> > 
> > -Michael
> > 
> > On Sun, 2017-11-19 at 18:04 +0100, Peter Müller wrote:
> > > Fixes #11519.
> > > 
> > > Signed-off-by: Peter Müller <peter.mueller(a)link38.eu>
> > > ---
> > >  html/cgi-bin/logs.cgi/ids.dat | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/html/cgi-bin/logs.cgi/ids.dat b/html/cgi-bin/logs.cgi/ids.dat
> > > index 44b3abdac..98176d690 100644
> > > --- a/html/cgi-bin/logs.cgi/ids.dat
> > > +++ b/html/cgi-bin/logs.cgi/ids.dat
> > > @@ -387,7 +387,7 @@ sub processevent
> > >  				}
> > >  				($title,$classification,$priority,$date,$
> > > time
> > > ,$srcip,$srcport,$destip,$destport, $sid) =
> > > ("n/a","n/a","n/a","n/a","n/a","n/a","n/a","n/a","n/a", "n/a");
> > >  				@refs = ();
> > > -				$_ =~ m/:([0-9]{1,4})\] (.*) \[\*\*\]/;
> > > +				$_ =~ m/:([0-9]{1,5})\] (.*) \[\*\*\]/;
> > >  				$title = &Header::cleanhtml($2,"y");
> > >  			}
> > >  			if ($_ =~ m/Classification: (.*)\] \[Priority:
> > > (\d)\]/) {  
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-11-21 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-19 17:04 Peter Müller
2017-11-20 15:49 ` Michael Tremer
2017-11-20 18:13   ` Peter Müller
2017-11-21 12:06     ` Michael Tremer [this message]

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=1511265969.4838.563.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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