From 9f806e97a24bba61417ae312fcc0da40914266fb Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Wed, 4 May 2011 21:35:41 +0200 Subject: Imported Upstream version 0.8.999 --- docs/api/network-manager-docs.xml | 129 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 docs/api/network-manager-docs.xml (limited to 'docs/api/network-manager-docs.xml') diff --git a/docs/api/network-manager-docs.xml b/docs/api/network-manager-docs.xml new file mode 100644 index 00000000..885ff7f1 --- /dev/null +++ b/docs/api/network-manager-docs.xml @@ -0,0 +1,129 @@ + + +]> + + + NetworkManager D-Bus Reference Manual + Version &version; + + + Dan + Williams + +
+ dcbw@redhat.com +
+ + + + + + 2011 + The NetworkManager Authors + + + + + 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 + version published by the Free Software Foundation with no + Invariant Sections, no Front-Cover Texts, and no Back-Cover + Texts. You may obtain a copy of the GNU Free + Documentation License from the Free Software + Foundation by visiting their Web site or by writing + to: + +
+ The Free Software Foundation, Inc., + 59 Temple Place - Suite 330, + Boston, MA 02111-1307, + USA +
+ + + + Many of the names used by companies to distinguish their + products and services are claimed as trademarks. Where those + names appear in any GNOME documentation, and those trademarks + are made aware to the members of the GNOME Documentation + Project, the names have been printed in caps or initial caps. + + + + + + D-Bus API Reference + + This part documents the D-Bus interface used to access the + NetworkManager daemon. + + + + + + Network Configuration Setting Specification + + This part documents the properties and value types of each "Setting" + object that composes the basic unit of NetworkManager configuration, + the "Connection". Each Connection object is simply a dictionary mapping + setting names (like "wimax" or "bluetooth") to a dictionary of + key/value pairs that represents each itself. + + +
+ Secret flag types + + Each secret property in a setting has an associated "flags" property + that describes how to handle that secret. The "flags" property is a + bitfield that contains zero or more of the following values logically + OR-ed together. + + + + + 0x0 (none) - the system is responsible for providing + and storing this secret. + + + 0x1 (agent-owned) - a user-session secret agent + is responsible for providing and storing this secret; when it is + required, agents will be asked to provide it. + + + 0x2 (not-saved) - this secret should not be saved + but should be requested from the user each time it is required. This + flag should be used for One-Time-Pad secrets, PIN codes from + hardware tokens, or if the user simply does not want to save the + secret. + + + 0x4 (not-required) - in some situations it cannot + be automatically determined that a secret is required or not. This + flag hints that the secret is not required and should not be + requested from the user. + + + +
+ + + + + + Index + + + + + + License + +FIXME: MISSING XINCLUDE CONTENT + + + + -- cgit 1.3.0-6-gf8a5