Summary: | vpnmain.cgi: special chars in passphrase breaks GUI and mix up fields | ||
---|---|---|---|
Product: | IPFire | Reporter: | Stefan Bauer <sb> |
Component: | --- | Assignee: | Stefan Schantl <stefan.schantl> |
Status: | CLOSED DUPLICATE | QA Contact: | Peter Müller <peter.mueller> |
Severity: | Minor Usability | ||
Priority: | Will affect an average number of users | CC: | adolf.belka, michael.tremer, mw+ipfire, peter.mueller, stefan.schantl, ummeegge |
Version: | 2 | ||
Hardware: | all | ||
OS: | All | ||
See Also: | https://bugzilla.ipfire.org/show_bug.cgi?id=11162 |
Description
Stefan Bauer
2018-05-17 07:57:34 UTC
I can confirm this behaviour, which also happens for PKCS12 passwords. This seems to be applicable for OpenVPN, too (https://community.ipfire.org/t/problem-installation-openvpn/2146/4), which is why I cc'ed Erik. Hi all, (In reply to Peter Müller from comment #2) > This seems to be applicable for OpenVPN, too > (https://community.ipfire.org/t/problem-installation-openvpn/2146/4), which > is why I cc'ed Erik. am running currently an OpenPVN-2.5_DEV version but this should makes no difference causing your mentioned PKCS#12 problem which i can not reproduce here. Have tried it with ' ~!@#%^*_+-={}[]:,./`$&()|\";'<>? ' but also with the in here mentioned combination ' 53503h30h3f%&$§0j0f3hf03fh3fh#?!')( ' and have here no problem with this at all. Am currently also not sure what exactly your problem is since an detailed description is missing. But this is related only for OpenVPN! Best, Erik This bit me too a while ago -- a PSK I got from another vendor contained a comma, which broke IPSec. That problem appeared because the /var/ipfire/vpn/config file is comma delimited, but input is not checked. Entering a comma (and, possibly, other special characters) in any field in the GUI destroys any future parsing of that file, assigning the completely wrong parameters to stuff. :-) This includes going from the first screen to the "advanced" one, as the latter screen depends on input in the first. The fastest and laziest way of countering this is by doing a JavaScript check at form submission, but this will of course not cure the real problem (and not for non-JS users). Some form of character escaping for this file would fix the problem permanently. *** This bug has been marked as a duplicate of bug 13209 *** *** This bug has been marked as a duplicate of bug 13029 *** @mangrove Thanks for correcting the duplicate bug number. |