Clean up i386/x86-64 cpuid usage in hwfeatures.c

[libgcrypt.git] / TODO

diff --git a/TODO b/TODO
index da1ef22..ffadc06 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-What's left to do                                 -*- outline -*-
+# What's left to do                                 -*- org -*-
 
 * Next API break:
 ** gcry_ac_io_t
@@ -12,10 +12,6 @@ What's left to do                                 -*- outline -*-
   This requires the introduction of a parameter names (say) U which
   is calculated according to OpenSSL/PKCS#1 rules.
 
-* Add a warning to the manual, to check that libgcrypt actually has
-  been compiled with thread support when used by a threaded
-  application.
-
 * linker script test
   Write an autoconf test to check whether the linker supports a
   version script. 
@@ -26,32 +22,6 @@ What's left to do                                 -*- outline -*-
   Don't rely on the secure memory based wiping function but add an
   extra wiping.
   
-* update/improve documentation
-** it's outdated for e.g. gcry_pk_algo_info.
-** document algorithm capabilities
-** Init requirements for random
-   The documentation says in "Controlling the library" that some
-   functions can only be used at initialization time, but it does not
-   explain what that means.  Initialization is a multi-step procedure:
-   First the thread callbacks have to be set up (optional), then the
-   gcry_check_version() function must be called (mandatory), then
-   further functions can be used.
-
-   The manual also says that something happens when the seed file is
-   registered berfore the PRNG is initialized, but it does not say how
-   one can guarantee to call it early enough.
-
-   Suggested fix: Specify initialization time as the time after
-   gcry_check_version and before calling any other function except
-   gcry_control().
-
-   All functions which modify global state without a lock must be
-   documented as "can only be called during initialization time" (but
-   see item 1).  Then the extraneous calls to _gcry_random_initialize
-   in gcry_control() can be removed, and the comments "not thread
-   safe" in various initialization-time-only functions like
-   _gcry_use_random_daemon become superfluous.
-
 * Use builtin bit functions of gcc 3.4
 
 * Consider using a daemon to maintain the random pool
@@ -66,28 +36,6 @@ What's left to do                                 -*- outline -*-
   collectros need to run that bunch of Unix utilities we don't waste
   their precious results.
 
-* Add transient flag to RSA key generation
- For short living keys it makes sense to allow generation using a PRNG.
- We could implement it this way:
-
- (genkey
-   (rsa
-     (nbits 4:1024)
-     (transient-key)))
-
-
-* Out of memory handler for secure memory should do proper logging
-
-  There is no shortage of standard memory, so logging is most likely
-  possible.
-
-* mpi_print does not use secure memory
-  for internal variables.
-
-* gcry_mpi_lshift is missing
-
-* Add OAEP
-
 * gcryptrnd.c
   Requires a test for pth [done] as well as some other tests.
 
@@ -109,5 +57,3 @@ What's left to do                                 -*- outline -*-
 ** C++ tests
   We have some code to allow using libgcrypt from C++, so we also
   should have a test case.
-
-* Use aliases for symbol instead of the wrappers in visibility.c.