Bug #8096: Special characters not propagated by the config sync engine - pfSense - pfSense bugtracker

Actions

Copy link

Bug #8096

closed

Special characters not propagated by the config sync engine

Added by Marin Bernard about 7 years ago. Updated over 3 years ago.

Status:

Duplicate

Priority:

Normal

Assignee:

Category:

XMLRPC

Target version:

Start date:

11/15/2017

Due date:

% Done:

Estimated time:

Plus Target Version:

Release Notes:

Default

Affected Version:

2.4.1

Affected Architecture:

All

Description

Hi,

We use configuration synchronisation between two pfSense boxes to sync a list of firewall aliases and rules. These objects include description strings with special characters (mainly French letters with accents).

On the backup node, those characters are always replaced by a space.

This issue does not exist with the backup/restore feature, which embeds special chars as HTML entities. However, it seems the configuration sync engine is unable to handle them properly on config update.

Actions

Copy link

Updated by Jens Groh over 6 years ago

Version 2.4-latest

I'll second this. The description field does not seem to be properly escaped when syncing to the standby node. We also use the field for better sortability and descriptions often inlucding a hostname like host.name.tld and separating infos with a pipe | and/or round brackets (). All these symbols .|() are replaced by spaces on the secondary node so we can not sort on the standby node like on the primary. Please include escaping the description field(s) to support more characters at least like dots . and pipes |

Thanks and kind regards,

Jens

Actions

Copy link