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/html/secrets-flags.html | 64 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) create mode 100644 docs/api/html/secrets-flags.html (limited to 'docs/api/html/secrets-flags.html') diff --git a/docs/api/html/secrets-flags.html b/docs/api/html/secrets-flags.html new file mode 100644 index 00000000..ee0a78fe --- /dev/null +++ b/docs/api/html/secrets-flags.html @@ -0,0 +1,64 @@ + + + + +Secret flag types + + + + + + + + + + + + + + + + +
+

+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. +
    • +
+

+

+
+
+
+ Generated by GTK-Doc V1.17
+ + \ No newline at end of file -- cgit 1.3.0-6-gf8a5