Summary: | OVPN Roadwarrior statistics graph failed | ||
---|---|---|---|
Product: | IPFire | Reporter: | Silvio <silvio.schloeffel> |
Component: | --- | Assignee: | Leo Hofmann <hofmann> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Aesthetic Issue | ||
Priority: | - Unknown - | CC: | adolf.belka, michael.tremer, morlix, peter.mueller |
Version: | 2 | ||
Hardware: | x86_64 | ||
OS: | Unspecified |
Description
Silvio
2021-05-07 10:04:56 UTC
@Leo: Would this be one for you? (In reply to Michael Tremer from comment #1) > @Leo: Would this be one for you? Yes, this is probably due to my parameter checking. I used quite strict regular expressions, because I did not expect that someone would put spaces in the graph parameters. I'll take a look at it. Hello Leo, it was not my goal to put spaces in the parameters. I see additional problems with the usage of the "remarks" field because i'm not sure if this field is unique. Silvio Hi Silvio, sorry, I did not make that clear. You (the user) should of course be able to put spaces in the "remarks" field without worrying about it! I expected OVPN to generate sanitized parameters from the input. On my test system, OVPN uses the subject CN ("User's full name or system hostname") field of the SSL certificate in the collectd path. I could not get it to use the "remarks" field. This is good because SSL ensures that the "subject" field is unique. I'll submit a patch to allow more non-word characters in the graph URL. Unfortunately, the ovpnmain.cgi is very complicated. I don't think I'll be able to change the underlying issue without breaking more stuff. But I agree that using the "name" field would be the way to go. Leo *** Bug 12624 has been marked as a duplicate of this bug. *** Fixed in IPFire Release 157 |