Feature #5602
closed
OpenVPN - certificate purpose validation required
100%
Description
Way too many threads every week with users posting about "my OpenVPN does not work", boiling down to
error=unsupported certificate purpose
I can see cert_get_purpose() in certs.inc, this or some similar function should be used to validate the OpenVPN server/client configuration before letting users save it.
Updated by Jim Pingle over 6 years ago
The problem with that is that it's not technically a requirement to use a server cert -- it's only required if the clients verify the server certificate type (which the export package does)
So we could be better about highlighting which certs are server certs (perhaps listing them first or styling them in some way) but we unfortunately we can't stop listing non-server certs there or it could break some setups.
We could also have the export package test the server cert type and omit the directive if they didn't use one, but I'd rather not encourage that practice too much.
Updated by Jim Thompson over 6 years ago
- Tracker changed from Bug to Feature
- Assignee set to Jim Pingle
Updated by Jim Pingle over 6 years ago
- Assignee changed from Jim Pingle to Anonymous
- Priority changed from Normal to Very Low
- % Done changed from 0 to 80
I pushed a change to separate, identify, and prioritize the servers in the list of certificates on the page. Passing this off to Steve Beaver since he had an idea for printing a pretty warning if they pick the wrong kind.
I'll also look into adding a warning to the OpenVPN client export package in the meantime.
Lowering the priority since the formatting isn't a huge concern now that the rest of the work has been done.
Updated by Anonymous over 6 years ago
- Status changed from New to Feedback
- Assignee changed from Anonymous to Jim Pingle
Dynamically update the help text based on the cert selected.
Updated by Anonymous over 6 years ago
- % Done changed from 80 to 100
Applied in changeset a4ba0282e6cba7916e3955f2d44da9a902f80587.
Updated by Jim Pingle over 6 years ago
- Status changed from Feedback to Resolved
Looks great, should hopefully be obvious enough to make people realize they did something incorrectly. :-)