Project

General

Profile

Actions
Copy link

Bug #7555

closed
JP RB

Snort settings show translation metadata when creating a new interface that is not yet defined

Bug #7555: Snort settings show translation metadata when creating a new interface that is not yet defined

Added by Jim Pingle over 9 years ago. Updated over 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Renato Botelho
Category:
Snort
Target version:
pfSense - 2.4.0
Start date:
05/17/2017
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.4
Affected Plus Version:
Affected Architecture:
All

Description

A few places in snort call gettext("{$if_friendly}") but that ends up showing translation metadata when it is a new interface that has not yet been saved/enabled.

Example, the breadcrumbs when creating a new interface show:

    Services / Snort / Edit Interface / Project-Id-Version: PACKAGE VERSION Report-Msgid-Bugs-To: POT-Creation-Date: 2017-05-16 09:23-0300 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PO-Revision-Date: 2017-02-03 05:17-0500 Last-Translator: Jim Thompson Language-Team: English (United States) Language: en-US X-Generator: Zanata 3.9.6 Plural-Forms: nplurals=2; plural=(n != 1)

In this case, $if_friendly is NULL when gettext is called.

BM Updated by Bill Meeks over 9 years ago Actions
Copy link
 #1

This is fixed in Snort GUI package version 3.2.9.3. The value is checked, and if NULL, the string "None" is substituted instead. This issue can be closed.

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #2

  • Status changed from New to Resolved

This is working in the current package. Thanks!

JP Updated by Jim Pingle over 9 years ago Actions
Copy link
 #3

You might consider changing "None" to "New Interface" or something like that as otherwise the tab names could be confusing to users.

BM Updated by Bill Meeks over 9 years ago Actions
Copy link
 #4

Jim Pingle wrote:

You might consider changing "None" to "New Interface" or something like that as otherwise the tab names could be confusing to users.

Good idea. I will do that in the next update. I suspect the same issue exists in the Suricata package as well, since they share a bunch of GUI code. I will fix it there, too.

Bill

Actions
Copy link

Also available in: Atom