viff

changeset 1103:24ba1dae612d

Added some future plans.
author Martin Geisler <mg@daimi.au.dk>
date Thu, 19 Feb 2009 16:16:46 +0100
parents 3442612fee88
children f12590662f93
files doc/index.txt doc/todo.txt
diffstat 2 files changed, 36 insertions(+), 0 deletions(-) [+]
line diff
     1.1 --- a/doc/index.txt	Tue Feb 17 09:42:09 2009 +0100
     1.2 +++ b/doc/index.txt	Thu Feb 19 16:16:46 2009 +0100
     1.3 @@ -32,6 +32,7 @@
     1.4     install
     1.5     implementation
     1.6     background
     1.7 +   todo
     1.8     coding-style
     1.9     development
    1.10     unit-testing
     2.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     2.2 +++ b/doc/todo.txt	Thu Feb 19 16:16:46 2009 +0100
     2.3 @@ -0,0 +1,35 @@
     2.4 +
     2.5 +Planned Work on VIFF
     2.6 +====================
     2.7 +
     2.8 +This document collects the bigger pieces of work we plan to do on
     2.9 +VIFF --- pieces too big for the bug tracker.
    2.10 +
    2.11 +
    2.12 +Active Security
    2.13 +---------------
    2.14 +
    2.15 +The protocol implemented in :mod:`viff.active` is (believed to be)
    2.16 +secure against active adversaries, but only as long as they don't
    2.17 +actually try to cheat! In other words, the players will crash in bad
    2.18 +ways if malformed data is received or too few shares are received.
    2.19 +
    2.20 +The following points should be addressed:
    2.21 +
    2.22 +* Error correction. The honest players must tolerate being sent wrong
    2.23 +  shares or no shares at all from the corrupt players.
    2.24 +
    2.25 +  This is related to Issue4_, Issue29_, and Issue70_.
    2.26 +
    2.27 +  .. _Issue4: http://tracker.viff.dk/issue4
    2.28 +  .. _Issue29: http://tracker.viff.dk/issue29
    2.29 +  .. _Issue70: http://tracker.viff.dk/issue70
    2.30 +
    2.31 +* Byzantine agreement. After the preprocessing phase a Byzantime
    2.32 +  agreement protocol should be run in order to determine if all honest
    2.33 +  players are ready to continue.
    2.34 +
    2.35 +  At the moment an honest players simply aborts the protocol if it
    2.36 +  detects any form of cheating --- the "idea" being that this will
    2.37 +  make the other honest players crash too, thereby effectively halting
    2.38 +  the protocol.