After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705792 - Support for inline ca/key/cert
Support for inline ca/key/cert
Status: RESOLVED DUPLICATE of bug 633337
Product: NetworkManager
Classification: Platform
Component: VPN: openvpn
git master
Other Linux
: Normal enhancement
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2013-08-11 11:41 UTC by Thomas Bechtold
Modified: 2015-05-29 05:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Thomas Bechtold 2013-08-11 11:41:55 UTC 
Would be cool if NetworkManager adds support for inline ca/key/cert. OpenVPN supports client configuration where you just need one file. the file looks like:

...
ca   [inline]
key  [inline]
cert [inline]


<ca>
-----BEGIN CERTIFICATE-----
XYZ
-----END CERTIFICATE-----
</ca>
<cert>
XYZ
</cert>
<key>
-----BEGIN PRIVATE KEY-----
XYZ
-----END PRIVATE KEY-----
</key>
Comment 1 tux.martin 2013-10-17 11:13:02 UTC 
From OpenVPN web: https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage#lbAV

INLINE FILE SUPPORT
OpenVPN allows including files in the main configuration for the --ca, --cert, --dh, --extra-certs, --key, --pkcs12, --secret and --tls-auth options.
Each inline file started by the line <option> and ended by the line </option>

Here is an example of an inline file usage

<cert>
-----BEGIN CERTIFICATE-----
[...]
-----END CERTIFICATE-----
</cert>
When using the inline file feature with --pkcs12 the inline file has to be base64 encoded. Encoding of a .p12 file into base64 can be done for example with OpenSSL by running openssl base64 -in input.p12
Comment 2 Thomas Haller 2015-05-29 05:49:15 UTC 
this is already reported

*** This bug has been marked as a duplicate of bug 633337 ***