private_key

Contains the private key when the eap property is set to "tls".

Key data is specified using a "scheme"; two are currently supported: blob and path. When using the blob scheme and private keys, this property should be set to the key's encrypted PEM encoded data. When using private keys with the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte. When using PKCS#<!-- -->12 format private keys and the blob scheme, this property should be set to the PKCS#<!-- -->12 data and the private_key_password property must be set to password used to decrypt the PKCS#<!-- -->12 certificate and key. When using PKCS#<!-- -->12 files and the path scheme, this property should be set to the full UTF-8 encoded path of the key, prefixed with the string "file://" and ending with a terminating NUL byte, and as with the blob scheme the "private-key-password" property must be set to the password used to decode the PKCS#<!-- -->12 private key and certificate.

Setting this property directly is discouraged; use the set_private_key function instead.

WARNING: private_key is not a "secret" property, and thus unencrypted private key data using the BLOB scheme may be readable by unprivileged users. Private keys should always be encrypted with a private key password to prevent unauthorized access to unencrypted private key data.