update

svn path=/trunk/kdesupport/qca/; revision=648931

TODO

@@ -9,19 +9,34 @@
   Change Doxyfile config to capture whole API, and to generate Latex manual.
 
 * beta3
-  api:
-    make sure there aren't any cases where a Foo::supportsBar()-style function
-      reports true, but then when the object is created, it doesn't actually
-      support the feature (because the wrong provider was used).
   code:
-    strange backtrace on mac (ask textshell)
-  other:
-    link against our own lib (e.g. -L../../lib) before ALL other libs,
-      including Qt's libs, since some distros put qca into qt's dir.
+    strange backtrace on mac ( http://flyspray.psi-im.org/task/640 )
 
 * beta4
   api:
+    some functions report availability of "sub"features without having context
+      with a specific provider (that is, the functions are not members of an
+      instance owned by a provider, nor is a provider necessarily specified
+      as an argument to the function).  in these cases, if a feature is
+      reported as being available, it is not clear how the app can actually
+      use the feature.  For example, if the static method TLS::canCompress()
+      returns true, it is entirely possible that when the application creates
+      a "new TLS;" instance, it won't be served by a provider that supports
+      compression.  possibly offending functions:
+    qca_publickey.h:
+      supportedGroupSets
+      supportedTypes
+      supportedIOTypes
+      supportedPBEAlgorithms
+    qca_cert.h:
+      canUseFormat
+      canUsePKCS7
+    qca_securelayer.h
+      supportedCipherSuites
+      canCompress
     cert extensions
+    crl URIs
+    policy info beyond OID
     OCSP ?
     random: either find a way to always provide good random numbers,
             or add an indicator as to whether the numbers can be
@@ -44,6 +59,7 @@
     constraints stuff seems messed up.  why are constraints auto-added by
       qca-openssl?
   other:
+    krazy warnings
     Update to latest Botan, and remake the botantools patch as appropriate
        - remove u32bit miller_rabin_test_iterations(u32bit bits, bool verify)
     ability to compile plugins in statically (check 'plugins' subdir)
@@ -62,6 +78,8 @@
     qca-cyrus-sasl has a problem where we can create the provider, and not create
     a saslContext, and then the destructor depends on uninitialised values (to
     see this, valgrind staticunittest).
+    link against our own lib (e.g. -L../../lib) before ALL other libs,
+      including Qt's libs, since some distros put qca into qt's dir?
   alon:
     log facility, with log level and a print destination (maybe file property?)
       figure out overlap with "diagnosticText"