Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free
Documentation License, Version 1.1 or any later
@@ -61,25 +61,25 @@
This section details the architectural and D-Bus API changes in
NetworkManager 0.9.
-Elimination of the User Settings Service
+Elimination of the User Settings Service
Previously there were two "settings services", or D-Bus services that
provided and saved network configuration information. NetworkManager
@@ -103,7 +103,7 @@
-User Secret Agents
+User Secret Agents
Even with the elimination of the user settings service, in some cases it
is still desirable to store secrets in the user's session and not in
@@ -152,7 +152,7 @@
-Settings Service Interface Changes
+Settings Service Interface Changes
With the elimination of the user settings service, the old
org.freedesktop.NetworkManagerUserSettings and
@@ -188,7 +188,7 @@
-Connection Object Interface Changes
+Connection Object Interface Changes
Consistent with the interface changes to the Settings object, the
Connection object's D-Bus interface has changed to
@@ -222,7 +222,7 @@
-Permissions Methods Consolidation
+Permissions Methods Consolidation
Previously there were two D-Bus method calls to retrieve the list of
operations that a user client could perform, and two signals notifying
@@ -254,7 +254,7 @@
are now string-based permissions. The mapping is as follows:
-
Table 17.
+
Table 17.
@@ -305,7 +305,7 @@
-AddConnection Returns Object Path of New Connection
+AddConnection Returns Object Path of New Connection
Many new mobile broadband devices support multiple access families, like
Qualcomm Gobi cards (CDMA/EVDO and GSM/UMTS), or multi-mode EVDO/LTE
@@ -413,7 +413,7 @@
-Secret Property Flags
+Secret Property Flags
In the Connection object's configuration properties, each setting's secret
properties (like WiFi passphrases, or public key passwords, etc) now has
@@ -422,7 +422,7 @@
following values:
-
Table 18.
+
Table 18.
@@ -484,7 +484,7 @@
-Deprecated Methods Removed
+Deprecated Methods Removed
A few methods and signals of the org.freedesktop.NetworkManager
interface deprecated in version 0.7 have been removed. All the
@@ -494,7 +494,7 @@
their replacements:
UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the 'ca-cert' property.
+
subject-match
+
string
+
+
Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed.
+
+
+
altsubject-matches
+
array of string
+
[]
+
List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.
+
+
client-cert
byte array
[]
@@ -139,10 +151,22 @@
UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the 'phase2-ca-cert' property.
+
phase2-subject-match
+
string
+
+
Substring to be matched against the subject of the certificate presented by the authentication server during the inner 'phase2' authentication. When unset, no verification of the authentication server certificate's subject is performed.
+
+
+
phase2-altsubject-matches
+
array of string
+
[]
+
List of strings to be matched against List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner 'phase 2' authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.
+
+
phase2-client-cert
byte array
[]
-
Contains the 'phase 2' client certificate if used by the EAP method specified in the 'phase2-eap' or 'phase2-autheap' properties. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte.
+
Contains the 'phase 2' client certificate if used by the EAP method specified in the 'phase2-auth' or 'phase2-autheap' properties. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte.
password
@@ -178,7 +202,7 @@
phase2-private-key
byte array
[]
-
Contains the 'phase 2' inner private key when the 'phase2-eap' 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 NULL 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 NULL 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.
+
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 NULL 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 NULL 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
@@ -204,7 +228,7 @@
-
Table 2. bluetooth setting
+
Table 2. bluetooth setting
@@ -243,7 +267,7 @@
-
Table 3. cdma setting
+
Table 3. cdma setting
@@ -294,7 +318,7 @@
-
Table 4. connection setting
+
Table 4. connection setting
@@ -363,7 +387,7 @@
-
Table 5. gsm setting
+
Table 5. gsm setting
@@ -388,7 +412,7 @@
number
string
-
Number to dial when establishing a PPP data session with the GSM-based mobile broadband network. In most cases, leave the number blank and a number selecting the APN specified in the 'apn' property will be used automatically when required.
+
Number to dial when establishing a PPP data session with the GSM-based mobile broadband network. Many modems do not require PPP for connections to the mobile network and thus this property should be left blank, which allows NetworkManager to select the appropriate settings automatically.
username
@@ -456,7 +480,7 @@
-
Table 6. ipv4 setting
+
Table 6. ipv4 setting
@@ -555,7 +579,7 @@
-
Table 7. ipv6 setting
+
Table 7. ipv6 setting
@@ -627,7 +651,7 @@
may-fail
boolean
-
FALSE
+
TRUE
If TRUE, allow overall network configuration to proceed even if IPv6 configuration times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv4-only networks, setting this property to TRUE allows the overall network configuration to succeed if IPv6 configuration fails but IPv4 configuration completes successfully.
@@ -636,7 +660,7 @@
-
Table 8. 802-11-olpc-mesh setting
+
Table 8. 802-11-olpc-mesh setting
@@ -681,7 +705,7 @@
-
Table 9. ppp setting
+
Table 9. ppp setting
@@ -816,7 +840,7 @@
-
Table 10. pppoe setting
+
Table 10. pppoe setting
@@ -867,7 +891,7 @@
-
Table 11. serial setting
+
Table 11. serial setting
@@ -924,7 +948,7 @@
-
Table 12. vpn setting
+
Table 12. vpn setting
@@ -955,7 +979,7 @@
user-name
string
-
User name of the currently logged in user for connections provided by the user settings service. This name is provided to the VPN plugin to use in lieu of a custom username provided by that VPN plugins specific configuration. The VPN plugin itself decides which user name to use.
+
If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.
data
@@ -975,7 +999,7 @@
-
Table 13. wimax setting
+
Table 13. wimax setting
@@ -1014,7 +1038,7 @@
-
Table 14. 802-3-ethernet setting
+
Table 14. 802-3-ethernet setting
@@ -1072,6 +1096,12 @@
If specified, request that the device use this MAC address instead of its permanent MAC address. This is known as MAC cloning or spoofing.
+
mac-address-blacklist
+
array of string
+
[]
+
If specified, this connection will never apply to the ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+
+
mtu
uint32
0
@@ -1079,7 +1109,7 @@
s390-subchannels
-
GPtrArray_gchararray_
+
array of string
[]
Identifies specific subchannels that this network device uses for communcation with z/VM or s390 host. Like the 'mac-address' property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.
@@ -1101,7 +1131,7 @@
-
Table 15. 802-11-wireless setting
+
Table 15. 802-11-wireless setting
@@ -1177,6 +1207,12 @@
If specified, request that the WiFi device use this MAC address instead of its permanent MAC address. This is known as MAC cloning or spoofing.
+
mac-address-blacklist
+
array of string
+
[]
+
If specified, this connection will never apply to the WiFi device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+
+
mtu
uint32
0
@@ -1186,7 +1222,7 @@
seen-bssids
array of string
[]
-
A list of BSSIDs (each BSSID formatted as a MAC address like '00:11:22:33:44:55') that have been detected as part of the WiFI network. The settings service will usually populate this property by periodically asking NetworkManager what the device's current AP is while connected to the network (or monitoring the device's 'active-ap' property) and adding the current AP's BSSID to this list. This list helps NetworkManager find hidden APs by matching up scan results with the BSSIDs in this list.
+
A list of BSSIDs (each BSSID formatted as a MAC address like 00:11:22:33:44:55') that have been detected as part of the WiFI network. NetworkManager internally tracks previously seen BSSIDs so this property is no longer of much use.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
diff --git a/docs/api/settings-spec.xml b/docs/api/settings-spec.xml
index 6be79b15..fd320b63 100644
--- a/docs/api/settings-spec.xml
+++ b/docs/api/settings-spec.xml
@@ -52,6 +52,18 @@
UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the 'ca-cert' property.
+
+ subject-match
+ string
+
+ Substring to be matched against the subject of the certificate presented by the authentication server. When unset, no verification of the authentication server certificate's subject is performed.
+
+
+ altsubject-matches
+ array of string
+ []
+ List of strings to be matched against the altSubjectName of the certificate presented by the authentication server. If the list is empty, no verification of the server certificate's altSubjectName is performed.
+ client-certbyte array
@@ -100,11 +112,23 @@
UTF-8 encoded path to a directory containing PEM or DER formatted certificates to be added to the verification chain in addition to the certificate specified in the 'phase2-ca-cert' property.
+
+ phase2-subject-match
+ string
+
+ Substring to be matched against the subject of the certificate presented by the authentication server during the inner 'phase2' authentication. When unset, no verification of the authentication server certificate's subject is performed.
+
+
+ phase2-altsubject-matches
+ array of string
+ []
+ List of strings to be matched against List of strings to be matched against the altSubjectName of the certificate presented by the authentication server during the inner 'phase 2' authentication. If the list is empty, no verification of the server certificate's altSubjectName is performed.
+ phase2-client-certbyte array[]
- Contains the 'phase 2' client certificate if used by the EAP method specified in the 'phase2-eap' or 'phase2-autheap' properties. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte.
+ Contains the 'phase 2' client certificate if used by the EAP method specified in the 'phase2-auth' or 'phase2-autheap' properties. Certificate data is specified using a 'scheme'; two are currently supported: blob and path. When using the blob scheme (which is backwards compatible with NM 0.7.x) this property should be set to the certificate's DER encoded data. When using the path scheme, this property should be set to the full UTF-8 encoded path of the certificate, prefixed with the string 'file://' and ending with a terminating NULL byte.password
@@ -140,7 +164,7 @@
phase2-private-keybyte array[]
- Contains the 'phase 2' inner private key when the 'phase2-eap' 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 NULL 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 NULL 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.
+ 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 NULL 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 NULL 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
@@ -326,7 +350,7 @@
numberstring
- Number to dial when establishing a PPP data session with the GSM-based mobile broadband network. In most cases, leave the number blank and a number selecting the APN specified in the 'apn' property will be used automatically when required.
+ Number to dial when establishing a PPP data session with the GSM-based mobile broadband network. Many modems do not require PPP for connections to the mobile network and thus this property should be left blank, which allows NetworkManager to select the appropriate settings automatically.username
@@ -553,7 +577,7 @@
may-failboolean
- FALSE
+ TRUEIf TRUE, allow overall network configuration to proceed even if IPv6 configuration times out. Note that at least one IP configuration must succeed or overall network configuration will still fail. For example, in IPv4-only networks, setting this property to TRUE allows the overall network configuration to succeed if IPv6 configuration fails but IPv4 configuration completes successfully.
@@ -851,7 +875,7 @@
user-namestring
- User name of the currently logged in user for connections provided by the user settings service. This name is provided to the VPN plugin to use in lieu of a custom username provided by that VPN plugins specific configuration. The VPN plugin itself decides which user name to use.
+ If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.data
@@ -955,6 +979,12 @@
[]If specified, request that the device use this MAC address instead of its permanent MAC address. This is known as MAC cloning or spoofing.
+
+ mac-address-blacklist
+ array of string
+ []
+ If specified, this connection will never apply to the ethernet device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+ mtuuint32
@@ -963,7 +993,7 @@
s390-subchannels
- GPtrArray_gchararray_
+ array of string[]Identifies specific subchannels that this network device uses for communcation with z/VM or s390 host. Like the 'mac-address' property for non-z/VM devices, this property can be used to ensure this connection only applies to the network device that uses these subchannels. The list should contain exactly 3 strings, and each string may only be composed of hexadecimal characters and the period (.) character.
@@ -1054,6 +1084,12 @@
[]If specified, request that the WiFi device use this MAC address instead of its permanent MAC address. This is known as MAC cloning or spoofing.
+
+ mac-address-blacklist
+ array of string
+ []
+ If specified, this connection will never apply to the WiFi device whose permanent MAC address matches an address in the list. Each MAC address is in the standard hex-digits-and-colons notation (00:11:22:33:44:55).
+ mtuuint32
@@ -1064,7 +1100,7 @@
seen-bssidsarray of string[]
- A list of BSSIDs (each BSSID formatted as a MAC address like '00:11:22:33:44:55') that have been detected as part of the WiFI network. The settings service will usually populate this property by periodically asking NetworkManager what the device's current AP is while connected to the network (or monitoring the device's 'active-ap' property) and adding the current AP's BSSID to this list. This list helps NetworkManager find hidden APs by matching up scan results with the BSSIDs in this list.
+ A list of BSSIDs (each BSSID formatted as a MAC address like 00:11:22:33:44:55') that have been detected as part of the WiFI network. NetworkManager internally tracks previously seen BSSIDs so this property is no longer of much use.security
diff --git a/docs/api/spec.html b/docs/api/spec.html
index 4533e786..c8abf6ca 100644
--- a/docs/api/spec.html
+++ b/docs/api/spec.html
@@ -1,5 +1,5 @@
-NetworkManager D-Bus Interface Specification version 0.9
NetworkManager D-Bus Interface Specification
Version 0.9
Copyright (C) 2008 - 2011 Red Hat, Inc.
Copyright (C) 2008 - 2009 Novell, Inc.
+
NetworkManager D-Bus Interface Specification
Version 0.9.0
Copyright (C) 2008 - 2011 Red Hat, Inc.
Copyright (C) 2008 - 2009 Novell, Inc.
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
diff --git a/docs/api/version.xml b/docs/api/version.xml
index 02098219..ac39a106 100644
--- a/docs/api/version.xml
+++ b/docs/api/version.xml
@@ -1 +1 @@
-0.8.9997
+0.9.0
diff --git a/docs/libnm-glib/html/NMClient.html b/docs/libnm-glib/html/NMClient.html
index 26d99de0..48fe024f 100644
--- a/docs/libnm-glib/html/NMClient.html
+++ b/docs/libnm-glib/html/NMClient.html
@@ -62,6 +62,8 @@ enum GPtrArray * nm_client_get_devices (NMClient *client);
NMDevice * nm_client_get_device_by_path (NMClient *client,
const char *object_path);
+NMDevice * nm_client_get_device_by_iface (NMClient *client,
+ const char *iface);
void (*NMClientActivateFn) (NMClient *client,
NMActiveConnection *active_connection,
GError *error,
@@ -370,7 +372,35 @@ Gets a
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free
Documentation License, Version 1.1 or any later
@@ -130,6 +130,9 @@
+Parses key/value pairs from a file descriptor (normally stdin) passed by
+an applet when the applet calls the authentication dialog of the VPN plugin.
+
+
+
+
+
+
fd :
+
file descriptor to read from, usually stdin (0)
+
+
+
out_data :
+
on successful return, a hash table
+(mapping char*:char*) containing the key/value pairs of VPN data items. [out][transfer full]
+
+
+
+
out_secrets :
+
on successful return, a hash table
+(mapping char*:char*) containing the key/value pairsof VPN secrets. [out][transfer full]
+
+
+
+
Returns :
+
+TRUE if reading values was successful, FALSE if not
+Given a VPN secret key name, attempts to find the corresponding flags data
+item in data. If found, converts the flags data item to
+NMSettingSecretFlags and returns it.
+
+
+
+
+
+
data :
+
hash table containing VPN key/value pair data items
+
+
+
secret_name :
+
VPN secret key name for which to retrieve flags for
+
+
+
out_flags :
+
on success, the flags associated with secret_name. [out]
+
+
+
+
Returns :
+
+TRUE if the flag data item was found and successfully converted
+to flags, FALSE if not
Update the specified setting's secrets, given a hash table of secrets
intended for that setting (deserialized from D-Bus for example). Will also
extract the given setting's secrets hash if given a hash of hashes, as would
-be returned from nm_connection_to_hash().
+be returned from nm_connection_to_hash(). If setting_name is NULL, expects
+a fully serialized NMConnection as returned by nm_connection_to_hash() and
+will update all secrets from all settings contained in secrets.
ignore secrets for which
+the secret's flags indicate the secret is owned by a user secret agent
+(ie, the secret's flag includes NM_SETTING_SECRET_FLAG_AGENT_OWNED)
+
+
+
+
NM_SETTING_COMPARE_FLAG_IGNORE_NOT_SAVED_SECRETS
+
ignore secrets for which
+the secret's flags indicate the secret should not be saved to persistent
+storage (ie, the secret's flag includes NM_SETTING_SECRET_FLAG_NOT_SAVED)
+
+
+
+
+
+
+
NMSetting
typedef struct _NMSetting NMSetting;
@@ -350,11 +408,16 @@ It should only be accessed through the functions described below.
NMSettingSecretFlags flags,
GError **error);
+ /* Returns TRUE if the given property contains the same value in both settings */
+ gboolean (*compare_property) (NMSetting *setting,
+ NMSetting *other,
+ const GParamSpec *prop_spec,
+ NMSettingCompareFlags flags);
+
/* Padding for future expansion */
void (*_reserved1) (void);
void (*_reserved2) (void);
void (*_reserved3) (void);
- void (*_reserved4) (void);
} NMSettingClass;
@@ -368,8 +431,35 @@ It should only be accessed through the functions described below.
const GValue *value,
GParamFlags flags,
gpointer user_data);
-
the "subject-match" property. This is the
+substring to be matched against the subject of the authentication
+server certificate, or NULL no subject verification is to be
+performed.
+Adds an allowed alternate subject name match. Until at least one
+match is added, the altSubjectName of the remote authentication
+server is not verified.
+
the "phase2-subject-match" property. This is
+the substring to be matched against the subject of the "phase 2"
+authentication server certificate, or NULL no subject verification
+is to be performed.
+Adds an allowed alternate subject name match for "phase 2". Until
+at least one match is added, the altSubjectName of the "phase 2"
+remote authentication server is not verified.
+
password used to decrypt the private key, or NULL if the password
+
password used to decrypt the private key, or NULL if the password
is unknown. If the password is given but fails to decrypt the private key,
an error is returned.
@@ -1787,8 +2170,7 @@ an error is returned.
Returns :
the private key password used to decrypt the private key if
-previously set with nm_setting_802_1x_set_private_key_from_file(),
-nm_setting_802_1x_set_private_key_path(), or the
+previously set with nm_setting_802_1x_set_private_key(), or the
"private-key-password" property.
password used to decrypt the private key, or NULL if the password
+
password used to decrypt the private key, or NULL if the password
is unknown. If the password is given but fails to decrypt the private key,
an error is returned.
@@ -2012,8 +2394,7 @@ an error is returned.
Returns :
the private key password used to decrypt the private key if
-previously set with nm_setting_802_1x_set_phase2_private_key_from_file(),
-nm_setting_802_1x_set_phase2_private_key_path(), or the
+previously set with nm_setting_802_1x_set_phase2_private_key() or the
"phase2-private-key-password" property.
@@ -2066,6 +2447,17 @@ previously set with nm_setting_802_1x_set_phase2_private_
+List of strings to be matched against the altSubjectName of the
+certificate presented by the authentication server. If the list
+is empty, no verification of the server certificate's
+altSubjectName is performed.
+
+List of strings to be matched against the altSubjectName of the
+certificate presented by the authentication server during the
+inner "phase 2" authentication. If the list is empty, no
+verification of the server certificate's altSubjectName is
+performed.
+
@@ -2256,8 +2660,8 @@ properties. Setting this property directly is discouraged; use the
Private key data used by "phase 2" inner authentication methods.
+Substring to be matched against the subject of the certificate
+presented by the authentication server during the inner "phase
+2" authentication. When unset, no verification of the
+authentication server certificate's subject is performed.
+
+
Default value: NULL
+
+
+
The "private-key" property
"private-key" GArray_guchar_* : Read / Write
@@ -2329,6 +2745,18 @@ Flags indicating how to handle
+
+Substring to be matched against the subject of the certificate
+presented by the authentication server. When unset, no
+verification of the authentication server certificate's subject
+is performed.
+
@@ -2336,9 +2764,8 @@ When TRUE, overrides "phase2-ca-path" properties using the system CA directory
specified at configure time with the --system-ca-path switch. The
certificates in this directory are added to the verification chain in
-addition to any certificates specified by the "ca-cert",
-"ca-cert-path", "phase2-ca-cert" and
-"phase2-ca-cert-path" properties.
+addition to any certificates specified by the "ca-cert"
+and "phase2-ca-cert" properties.
+The NMSettingBluetooth object is a NMSetting subclass that describes
+properties necessary for connection to devices that provide network
+connections via the Bluetooth Dial-Up Networking (DUN) and Network Access
+Point (NAP) profiles.
the connection
+did not contain a required type setting, ie for DUN connections the connection
+must also contain an NMSettingGsm or NMSettingCdma as appropriate
+
-Either 'dun' for Dial-Up Networking connections (not yet supported) or
-'panu' for Personal Area Networking connections.
+Either 'dun' for Dial-Up Networking connections or 'panu' for Personal
+Area Networking connections to devices supporting the NAP profile.
Default value: NULL
diff --git a/docs/libnm-util/html/NMSettingCdma.html b/docs/libnm-util/html/NMSettingCdma.html
index 3dc4a712..1c93803d 100644
--- a/docs/libnm-util/html/NMSettingCdma.html
+++ b/docs/libnm-util/html/NMSettingCdma.html
@@ -105,16 +105,40 @@ networks, including those using CDMA2000/EVDO technology.
the required NMSettingSerial
+is missing in the connection
+
+
+
+
diff --git a/docs/libnm-util/html/NMSettingConnection.html b/docs/libnm-util/html/NMSettingConnection.html
index 2b113d2d..e0085a7c 100644
--- a/docs/libnm-util/html/NMSettingConnection.html
+++ b/docs/libnm-util/html/NMSettingConnection.html
@@ -577,7 +577,7 @@ the "user" permission type is supported, and pitem
+The NMSettingGsm object is a NMSetting subclass that describes
+properties that allow connections to 3GPP-based mobile broadband
+networks, including those using GPRS/EDGE and UMTS/HSPA technology.
@@ -255,7 +293,43 @@ const char * NMSettingGsmNetworkType values indicate the allowed access technologies
+the device may use when connecting to this network.
+
+
+
+
+
NM_SETTING_GSM_NETWORK_TYPE_ANY
+
any access technology may be used
+
+
+
+
NM_SETTING_GSM_NETWORK_TYPE_UMTS_HSPA
+
only 3G-type (UMTS and HSPA)
+technologies may be used
+
+
+
+
NM_SETTING_GSM_NETWORK_TYPE_GPRS_EDGE
+
only 2G-type (GPRS and EDGE)
+technologies may be used
+
+
+
+
NM_SETTING_GSM_NETWORK_TYPE_PREFER_UMTS_HSPA
+
3G-type technologies are
+preferred but 2G-type technologies may be used as a fallback
+
+
+
+
NM_SETTING_GSM_NETWORK_TYPE_PREFER_GPRS_EDGE
+
2G-type technologies are
+preferred but 3G-type technologies may be used as a fallback
+
+
+
+
@@ -275,10 +349,93 @@ const char * NMSettingGsmNetworkBand values indicate the allowed frequency bands
+the device may use when connecting to this network.
+
Bitfield of allowed frequency bands. Note that not all devices allow
-frequency band control.
+frequency band control. Permitted values are those specified by
+NMSettingGsmNetworkBand.
Allowed values: <= 1
Default value: 1
@@ -477,9 +751,9 @@ roaming control of the device is not otherwise possible.
Network preference to force the device to only use specific network
-technologies. The permitted values are: -1: any, 0: 3G only,
-1: GPRS/EDGE only, 2: prefer 3G, and 3: prefer 2G. Note that not all
-devices allow network preference control.
+technologies. Permitted values are those specified by
+NMSettingGsmNetworkType. Note that not all devices allow network
+preference control.
Number to dial when establishing a PPP data session with the GSM-based
-mobile broadband network. In most cases, leave the number blank and a
-number selecting the APN specified in the 'apn' property will be used
-automatically when required.
+mobile broadband network. Many modems do not require PPP for connections
+to the mobile network and thus this property should be left blank, which
+allows NetworkManager to select the appropriate settings automatically.
+TRUE if NetworkManager should send the machine hostname to the
+DHCP server when requesting addresses to allow the server to automatically
+update DNS information for this machine.
+TRUE if this connection doesn't require IPv6 addressing to complete
+for the connection to succeed.
+
+
+
@@ -886,7 +1671,7 @@ example, in IPv4-only networks, setting this property to TRUE allows
the overall network configuration to succeed if IPv6 configuration fails
but IPv4 configuration completes successfully.
-
+The NMSettingPPP object is a NMSetting subclass that describes properties
+necessary for connection to networks that require PPP transport, like PPPoE
+cable and DSL modems and some mobile broadband devices.
+The NMSettingPPPOE object is a NMSetting subclass that describes
+properties necessary for connection to networks that require PPPoE connections
+to provide IP transport, for example cable or DSL modems.
+The NMSettingSerial object is a NMSetting subclass that describes
+properties necessary for connections that may use serial communications,
+such as mobile broadband or analog telephone connections.
+The NMSettingVPN object is a NMSetting subclass that describes properties
+necessary for connection to Virtual Private Networks. NetworkManager uses
+a plugin architecture to allow easier use of new VPN types, and this
+setting abstracts the configuration for those plugins. Since the configuration
+options are only known to the VPN plugins themselves, the VPN configuration
+options are stored as key/value pairs of strings rather than GObject
+properties.
User name of the currently logged in user for connections provided by the user settings service. This name is provided to the VPN plugin to use in lieu of a custom username provided by that VPN plugins specific configuration. The VPN plugin itself decides which user name to use.
+
If the VPN connection requires a user name for authentication, that name should be provided here. If the connection is available to more than one user, and the VPN requires each user to supply a different name, then leave this property empty. If this property is empty, NetworkManager will automatically supply the username of the user which requested the VPN connection.
+If specified, this connection will only apply to the WiMAX device
+whose MAC address matches. This property does not change the MAC address
+of the device (known as MAC spoofing).
+
+Network Service Provider (NSP) name of the WiMAX network this connection
+should use.
+
+
Default value: NULL
+
+
+
+
+
+
\ No newline at end of file
diff --git a/docs/libnm-util/html/NMSettingWired.html b/docs/libnm-util/html/NMSettingWired.html
index d079de3a..dc01f965 100644
--- a/docs/libnm-util/html/NMSettingWired.html
+++ b/docs/libnm-util/html/NMSettingWired.html
@@ -35,13 +35,16 @@
NMSettingWired
-
NMSettingWired
+
NMSettingWired — Describes connection properties for Ethernet-based networks
+If specified, this connection will never apply to the ethernet device
+whose permanent MAC address matches an address in the list. Each
+MAC address is in the standard hex-digits-and-colons notation
+(00:11:22:33:44:55).
+
+Adds a new WiFi AP's BSSID to the previously seen BSSID list of the setting.
+NetworkManager tracks previously seen BSSIDs internally so this function
+no longer has much use.
+Given a NMSettingWireless and an optional NMSettingWirelessSecurity,
+determine if the configuration given by the settings is compatible with
+the security of an access point using that access point's capability flags
+and mode. Useful for clients that wish to filter a set of connections
+against a set of access points and determine which connections are
+compatible with which access points.
+
+
+If specified, this connection will never apply to the WiFi device
+whose permanent MAC address matches an address in the list. Each
+MAC address is in the standard hex-digits-and-colons notation.
+(00:11:22:33:44:55).
+
@@ -544,11 +872,8 @@ the connection contains a valid 802-11-wireless-security setting.
A list of BSSIDs (each BSSID formatted as a MAC address like
'00:11:22:33:44:55') that have been detected as part of the WiFI network.
-The settings service will usually populate this property by periodically
-asking NetworkManager what the device's current AP is while connected
-to the network (or monitoring the device's 'active-ap' property) and
-adding the current AP'sBSSID to this list. This list helps NetworkManager
-find hidden APs by matching up scan results with the BSSIDs in this list.
+NetworkManager internally tracks previously seen BSSIDs so this property
+is no longer of much use.
+The NMSettingWirelessSecurity object is a NMSetting subclass that describes
+properties necessary for connection to encrypted WiFi networks.
+
+
+It's a good idea to read up on wpa_supplicant configuration before using this
+setting extensively, since most of the options here correspond closely with
+the relevant wpa_supplicant configuration options. To get a better overview
+of how WiFi security works, you may want to get copies of the following books.
+
+
+ 802.11 Wireless Networks: The Definitive Guide, Second Edition
+ Author: Matthew Gast
+ ISBN: 978-0596100520
+
+
+ Cisco Wireless LAN Security
+ Authors: Krishna Sankar, Sri Sundaralingam, Darrin Miller, and Andrew Balinsky
+ ISBN: 978-1587051548
Shared Key
+authentication was specified but the setting did not specify WEP as the
+encryption protocol
+
+
+
+
@@ -239,7 +304,47 @@ const char * NMWepKeyType values specify how any WEP keys present in the setting
+are intepreted. There are no standards governing how to hash the various WEP
+key/passphrase formats into the actual WEP key. Unfortunately some WEP keys
+can be interpreted in multiple ways, requring the setting to specify how to
+interpret the any WEP keys. For example, the key "732f2d712e4a394a375d366931"
+is both a valid Hexadecimal WEP key and a WEP passphrase. Further, many
+ASCII keys are also valid WEP passphrases, but since passphrases and ASCII
+keys are hashed differently to determine the actual WEP key the type must be
+specified.
+
+
+
+
+
NM_WEP_KEY_TYPE_UNKNOWN
+
unknown WEP key type
+
+
+
+
NM_WEP_KEY_TYPE_KEY
+
indicates a hexadecimal or ASCII formatted WEP key.
+Hex keys are either 10 or 26 hexadecimal characters (ie "5f782f2f5f" or
+"732f2d712e4a394a375d366931"), while ASCII keys are either 5 or 13 ASCII
+characters (ie "abcde" or "blahblah99$*1").
+
+
+
+
NM_WEP_KEY_TYPE_PASSPHRASE
+
indicates a WEP passphrase (ex "I bought a duck
+on my way back from the market 235Q&^%^*%") instead of a hexadecimal or ASCII
+key. Passphrases are between 8 and 64 characters inclusive and are hashed
+the actual WEP key using the MD5 hash algorithm.
+
+Adds a WiFi security protocol (one of "wpa" or "rsn") to the allowed list;
+only protocols in this list will be used when finding and connecting to
+the WiFi network specified by this connection. For example, if the
+protocol list contains only "wpa" but the access point for the SSID specified
+by this connection only supports WPA2/RSN, the connection cannot be used
+with the access point.
+Adds an encryption algorithm to the list of allowed pairwise encryption
+algorithms. If the list is not empty, then only access points that support
+one or more of the encryption algorithms in the list will be considered
+compatible with this connection.
+Adds an encryption algorithm to the list of allowed groupwise encryption
+algorithms. If the list is not empty, then only access points that support
+one or more of the encryption algorithms in the list will be considered
+compatible with this connection.
-Controls the interpretation of WEP keys. Allowed values are 1 (interpret
-WEP keys as hexadecimal or ASCII keys) or 2 (interpret WEP keys as WEP
-Passphrases). If set to 1 and the keys are hexadecimal, they must be
+Controls the interpretation of WEP keys. Allowed values are those given
+by NMWepKeyType. If set to 1 and the keys are hexadecimal, they must be
either 10 or 26 characters in length. If set to 1 and the keys are
ASCII keys, they must be either 5 or 13 characters in length. If set to
2, the passphrase is hashed using the de-facto MD5 method to derive the
diff --git a/docs/libnm-util/html/api-index-full.html b/docs/libnm-util/html/api-index-full.html
index 0ea92385..f47ea2c9 100644
--- a/docs/libnm-util/html/api-index-full.html
+++ b/docs/libnm-util/html/api-index-full.html
@@ -21,10 +21,20 @@
-C
+8
+ |
+ A
+ |
+ B
+ |
+ C
+ |
+ D
|
I
|
+ M
+ |
S
|
T
@@ -39,7 +49,34 @@
API Index
-
C
+
8
+
+NM80211ApFlags, enum in NetworkManager
+
+
+
+NM80211ApSecurityFlags, enum in NetworkManager
+
+
+
+NM80211Mode, enum in NetworkManager
+
+
+
A
+
+NMActiveConnectionState, enum in NetworkManager
+
+
+
B
+
+NMBluetoothCapabilities, enum in NetworkManager
+
+NM_VPN_DBUS_PLUGIN_INTERFACE, macro in NetworkManagerVPN
+
+
+
+NM_VPN_DBUS_PLUGIN_PATH, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_ADDRESS, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_BANNER, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_DNS, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_DOMAIN, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_EXT_GATEWAY, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_GATEWAY, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_INT_GATEWAY, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_MSS, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_MTU, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_NBNS, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_NEVER_DEFAULT, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_PREFIX, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_PTP, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_ROUTES, macro in NetworkManagerVPN
+
+
+
+NM_VPN_PLUGIN_IP4_CONFIG_TUNDEV, macro in NetworkManagerVPN
+
+
W
NMWepKeyType, enum in NMSettingWirelessSecurity
diff --git a/docs/libnm-util/html/ch01.html b/docs/libnm-util/html/ch01.html
index 52f73af9..d97a8939 100644
--- a/docs/libnm-util/html/ch01.html
+++ b/docs/libnm-util/html/ch01.html
@@ -21,7 +21,7 @@
-libnm-util API Reference
+libnm-util API Reference
NMConnection — Describes a connection to specific network or provider
@@ -33,25 +33,30 @@
NMSettingConnection — Describes general connection properties