To do list  (a.k.a known problems)
---------------------------------

Although the current distribution of ITTC is stable there are few
improvements to be done in future versions.

* Stability
	I made a testscript: runtime/config/runtest.pl  which can be used to test the stability.
	At the moment, it fails about 50% of the time ...

* Memory leaks
	Generating a key >= 1500 bits eats up >100MB RAM per shareserver, which shouldn´t be the case.
	Memoryleaks can be traced with the runtime/config/myvalgrind script and the runtime/config/serverlog.* files

* Key splitting.
	Splitting an existing RSA key into a shared key, for migration.

* Key combining.
	Combining shared keys into a normal RSA key, for migration. 

* GnuPG support.
	Adding support for ITTC into GnuPG, so that GnuPG can also use shared keys

* Sequence numbers and multi-threading.
	The share servers treat the entire sequence number handshake
	protocol as a critical section.  No multi-threading takes place
	during sequence number handshake.  The semantics of threading 
	with sequence numbers is not well defined.  It is desirable to 
	reengineer the sequence number mechanism to handle multi-threading
	on both share servers and clients.

* Testing a refreshed key.
	When refresh generates a new sharing of an existing key the
	new sharing is committed to (namely, the old sharing is removed)
	and the resulting shares are tested.  These two steps should
	be done in the reverse order.  If the new sharing does not verify
	properly the system should fall back to the old sharing.

* Testing a newly generated key.
	The mechanism for testing a new key (TLB_TestServers) can be 
	greatly improved in terms of performance.  

* Monitor.
	Add functionality to the monitor utility.  In particular enable
	admin to choose what level of monitor messages to display.

* Key generation.
	Distributed key generation works with up to five servers.  Future
	releases will support more than 5 servers.