Feature #560
Does ipsec.conf syntax really need to remain so finicky?
Description
Periodically we have really strange issues which result because of a splattering of lines with just 1 space, throwing ipsec into a mass confusion if it comes after a commented connection section. Or if a comment within a section is not indented as the lines before of after.
It seems that continuing this strict formatting is not necessary these days. Can the logic be changed to just ignore whitespaces? Connection sections have to be clearly marked with a line of "conn", and it should probably just end at the next line with nothing but whitespace.
Whatever the rule.. it just seems like this archaic rule has no business remaining in the year 2014.
History
#1 Updated by Tobias Brunner over 11 years ago
- Status changed from New to Feedback
- Assignee set to Tobias Brunner
- Target version set to 5.2.0
To answer the question in the subject: No it does not. In fact, an updated parser has already been written and is intended to be released with 5.2.0.
#2 Updated by c b over 11 years ago
sweet!
#3 Updated by Tobias Brunner about 11 years ago
- Category set to starter
- Status changed from Feedback to Closed
- Resolution set to Fixed
Fixed with the associated merge.