From 2bfb3eb7d0323e69affca154395f51d8b577414d Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 6 Apr 2016 00:46:19 +0200 Subject: Imported Upstream version 1.1.93 --- docs/api/html/nm-settings.html | 89 ++++++++++++++++++++---------------------- 1 file changed, 43 insertions(+), 46 deletions(-) (limited to 'docs/api/html/nm-settings.html') diff --git a/docs/api/html/nm-settings.html b/docs/api/html/nm-settings.html index 7a9b75e9..3a540262 100644 --- a/docs/api/html/nm-settings.html +++ b/docs/api/html/nm-settings.html @@ -29,7 +29,7 @@
-

DESCRIPTION

+

Description

NetworkManager is based on a concept of connection profiles, sometimes referred to as connections only. These connection profiles contain a network configuration. When @@ -94,7 +94,7 @@

-

Table 31. 802-1x setting

+

Table 31. 802-1x setting

@@ -257,13 +257,13 @@ - + - + @@ -293,13 +293,13 @@ - + - + @@ -323,7 +323,7 @@
phase2-private-key byte array  Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" 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 PKCS12 format private keys and the blob scheme, this property should be set to the PKCS12 data and the "phase2-private-key-password" property must be set to password used to decrypt the PKCS12 certificate and key. When using PKCS12 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 and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS12 private key and certificate.Contains the "phase 2" inner private key when the "phase2-auth" or "phase2-autheap" 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 "phase2-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 and ending with a terminating NUL byte, and as with the blob scheme the "phase2-private-key-password" property must be set to the password used to decode the PKCS#12 private key and certificate.
phase2-private-key-password string  The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS12 format key.The password used to decrypt the "phase 2" private key specified in the "phase2-private-key" property when the private key either uses the path scheme, or is a PKCS#12 format key.
phase2-private-key-password-flagsprivate-key byte array  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 PKCS12 format private keys and the blob scheme, this property should be set to the PKCS12 data and the "private-key-password" property must be set to password used to decrypt the PKCS12 certificate and key. When using PKCS12 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 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 PKCS12 private key and certificate. 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.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 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. 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.
private-key-password string  The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS12 format key.The password used to decrypt the private key specified in the "private-key" property when the private key either uses the path scheme, or if the private key is a PKCS#12 format key.
private-key-password-flags

-

Table 32. adsl setting

+

Table 32. adsl setting

@@ -390,7 +390,7 @@

-

Table 33. bluetooth setting

+

Table 33. bluetooth setting

@@ -427,7 +427,7 @@

-

Table 34. bond setting

+

Table 34. bond setting

@@ -464,7 +464,7 @@

-

Table 35. bridge setting

+

Table 35. bridge setting

@@ -543,7 +543,7 @@

-

Table 36. bridge-port setting

+

Table 36. bridge-port setting

@@ -586,7 +586,7 @@

-

Table 37. cdma setting

+

Table 37. cdma setting

@@ -611,7 +611,7 @@ - + @@ -635,7 +635,7 @@
number string  The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (777) is used when required.The number to dial to establish the connection to the CDMA-based mobile broadband network, if any. If not specified, the default number (#777) is used when required.
password

-

Table 38. connection setting

+

Table 38. connection setting

@@ -762,7 +762,7 @@

-

Table 39. dcb setting

+

Table 39. dcb setting

@@ -877,7 +877,7 @@

-

Table 40. generic setting

+

Table 40. generic setting

@@ -900,7 +900,7 @@

-

Table 41. gsm setting

+

Table 41. gsm setting

@@ -997,7 +997,7 @@

-

Table 42. infiniband setting

+

Table 42. infiniband setting

@@ -1052,7 +1052,7 @@

-

Table 43. ipv4 setting

+

Table 43. ipv4 setting

@@ -1197,7 +1197,7 @@

-

Table 44. ipv6 setting

+

Table 44. ipv6 setting

@@ -1342,7 +1342,7 @@

-

Table 45. ip-tunnel setting

+

Table 45. ip-tunnel setting

@@ -1439,7 +1439,7 @@

-

Table 46. macvlan setting

+

Table 46. macvlan setting

@@ -1488,7 +1488,7 @@

-

Table 47. 802-11-olpc-mesh setting

+

Table 47. 802-11-olpc-mesh setting

@@ -1531,7 +1531,7 @@

-

Table 48. ppp setting

+

Table 48. ppp setting

@@ -1664,7 +1664,7 @@

-

Table 49. pppoe setting

+

Table 49. pppoe setting

@@ -1713,7 +1713,7 @@

-

Table 50. serial setting

+

Table 50. serial setting

@@ -1768,7 +1768,7 @@

-

Table 51. team setting

+

Table 51. team setting

@@ -1805,7 +1805,7 @@

-

Table 52. team-port setting

+

Table 52. team-port setting

@@ -1836,7 +1836,7 @@

-

Table 53. tun setting

+

Table 53. tun setting

@@ -1897,7 +1897,7 @@

-

Table 54. vlan setting

+

Table 54. vlan setting

@@ -1958,7 +1958,7 @@

-

Table 55. vpn setting

+

Table 55. vpn setting

@@ -2019,7 +2019,7 @@

-

Table 56. vxlan setting

+

Table 56. vxlan setting

@@ -2140,7 +2140,7 @@

-

Table 57. wimax setting

+

Table 57. wimax setting

@@ -2177,7 +2177,7 @@

-

Table 58. 802-3-ethernet setting

+

Table 58. 802-3-ethernet setting

@@ -2280,7 +2280,7 @@

-

Table 59. 802-11-wireless setting

+

Table 59. 802-11-wireless setting

@@ -2401,7 +2401,7 @@

-

Table 60. 802-11-wireless-security setting

+

Table 60. 802-11-wireless-security setting

@@ -2547,18 +2547,15 @@
-

AUTHOR

-

NetworkManager developers

+

Files

+

/etc/NetworkManager/system-connections or distro plugin-specific location

-

FILES

-

/etc/NetworkManager/system-connections

-

or distro plugin-specific location

-
-
-

SEE ALSO

-

https://wiki.gnome.org/Projects/NetworkManager/ConfigurationSpecification

-

NetworkManager(8), nmcli(1), nmcli-examples(5), NetworkManager.conf(5)

+

See Also

+

NetworkManager(8), + nmcli(1), + nmcli-examples(7), + NetworkManager.conf(5)

-- cgit 1.3.0-6-gf8a5