Project

General

Profile

Actions

Bug #3931

closed

Using international characters in IPsec PSK causes invalid XML

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

Status:
Resolved
Priority:
Normal
Category:
IPsec
Target version:
Start date:
10/13/2014
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

If an international character, such as à is added to an IPsec PSK, it will cause the configuration to contain invalid XML upon save and the system will restore the previous configuration.

Input validation should reject such characters, or the field should be CDATA encoded if they are valid.

This is broken in both 2.1.x and 2.2.

Actions #1

Updated by Chris Buechler over 9 years ago

#3431 and #3636 are effectively the same, closed those in favor of this.

Actions #2

Updated by Renato Botelho over 9 years ago

  • Assignee set to Renato Botelho
Actions #3

Updated by Renato Botelho over 9 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Pushed a fix 123d870060

Actions #4

Updated by Jim Pingle over 9 years ago

  • Status changed from Feedback to New

Seems to still allow some characters that can break XML (like à )

Actions #5

Updated by Renato Botelho over 9 years ago

  • Status changed from New to Feedback
Actions #6

Updated by Jim Pingle over 9 years ago

  • Status changed from Feedback to Resolved

Confirmed fixed for IPsec P1, PSK tab, and User PSK fields. Invalid characters are now properly rejected.

Actions

Also available in: Atom PDF