| Summary: | Usually an OpenVPN Server delivers .ovpn files, but they are not being used by network-manager applet | ||
|---|---|---|---|
| Product: | [Unmaintained] Network Management | Reporter: | ray-ven <gortab> |
| Component: | OpenVPN | Assignee: | Will Stephenson <wstephenson> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | wishlist | CC: | lamarque |
| Priority: | NOR | ||
| Version: | 0.9 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
As far as I know no Plasma NM developer has access to an openvpn server, I for example only have access to VPNC. I do not even know how openvpn works, which settings are required, which are optional, how to handle the certificate files, etc. If you know how to fix this problem please give us the steps as succint as possible because we won't be able to test the fix ourselves. *** This bug has been marked as a duplicate of bug 194099 *** |
Version: 0.9 (using KDE 4.6.4) OS: Linux I can't expect users to use difficult workarounds to get ca, cert, key pam files Workaround: #!/bin/bash P12FILE=${1##*/} NAME=${P12FILE%%.*} openssl pkcs12 -nocerts -in $P12FILE -out ${NAME}_key.pem openssl pkcs12 -nokeys -clcerts -in $P12FILE -out ${NAME}_cert.pem openssl pkcs12 -nokeys -cacerts -in $P12FILE -out ${NAME}_ca.pem Reproducible: Didn't try