CVS update: sierra/docs

From: cvs@openprivacy.org
Date: Fri Feb 09 2001 - 14:39:11 PST

  • Next message: cvs@openprivacy.org: "CVS update: sierra/src/java/org/openprivacy/sierra/nym/talon/interfaces"

    Date: Friday February 9, 19101 @ 14:39
    Author: burton
    CVSWEB Options: -------------------

    Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi

    View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs

    -----------------------------------

    Update of /usr/local/cvs/public/sierra/docs
    In directory giga:/tmp/cvs-serv24654/docs

    Modified Files:
            TODO
    Log Message:
    nym creation/abstrction mechanism

    *****************************************************************
    File: sierra/docs/TODO

    CVSWEB Options: -------------------

    CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?annotate=1.51

    CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO?rev=1.51&content-type=text/x-cvsweb-markup

    CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/sierra/docs/TODO.diff?r1=1.51&r2=1.50

    -----------------------------------

    Index: sierra/docs/TODO
    diff -u sierra/docs/TODO:1.50 sierra/docs/TODO:1.51
    --- sierra/docs/TODO:1.50 Fri Feb 9 02:26:57 2001
    +++ sierra/docs/TODO Fri Feb 9 14:39:11 2001
    @@ -1,6 +1,6 @@
     ********************************************************************************
    -*** Last-Modified: $Date: 2001/02/09 10:26:57 $
    -*** Version: $Id: TODO,v 1.50 2001/02/09 10:26:57 burton Exp $
    +*** Last-Modified: $Date: 2001/02/09 22:39:11 $
    +*** Version: $Id: TODO,v 1.51 2001/02/09 22:39:11 burton Exp $
     *** Author: Kevin A. Burton ( burton@apache.org | burton@openprivacy.org )
     ********************************************************************************
       
    @@ -17,10 +17,49 @@
     = ===============================================================================
     
     
    + - Need an abstraction of how to create and manage nyms. The facility needs a
    + way to get the private and public keys for the nym and also determine a new
    + nym based on another nym. This "new" nym could be used temporarily but
    + could also stay with the user for a long period of time with support for the
    + parent nym proving that it created this sub-nym. The system should support
    + basic nyms which are simple to implement but scales to PGP, RSA, etc. When
    + it comes time to rewrite this Sierra to support PGP/RSA we shouldn't have to
    + modify any of Sierra to support this.
    +
    + - need to provide an equals() method so that we can determine if two Ns are
    + the same.
    +
    + - Nym implements Principal -> Talon interface
    + +init() do whatever it takes to build this Num
    + +getPrivateKey
    + +getPublicKey
    + +getNym() get a child nym... based on this nym
    +
    + - KeyBuilder -> Talon interface... need to build more impls...
    + +getNym()
    + +getPropertyManager()
    +
    + - determine requirements for a data store... maybe this *should* be
    + something like jewel.
    +
    +
    + - need to build a Query type used to fetch an actual reputation value (not
    + getReputation). This should use the Hashcode of current objects.
    +
    +
    + - not every component within Sierra needs or should be under the 'talon'
    + package. Instead we should move these to their own package... Example. The
    + basic nym package should be under org.openprivacy.sierra.nym.talon. The
    + reputation interfaces should go under org.openprivacy.sierra.reputation.talon.
    +
    +
    +
    +
    +
    +
    +
     TODO:
     
    - - determine requirements for a data store... maybe this *should* be
    - something like jewel.
          -
     
                - maybe we should remove putReputation from the RCE and just have an
    @@ -72,18 +111,6 @@
         good example of this would be that anything that "Fen" says counts as 5
         votes in the ontology of "Privacy".
     
    - - Need an abstraction of how to create and manage nyms. The facility needs a
    - way to get the private and public keys for the nym and also determine a new
    - nym based on another nym. This "new" nym could be used temporarily but
    - could also stay with the user for a long period of time with support for the
    - parent nym proving that it created this sub-nym. The system should support
    - basic nyms which are simple to implement but scales to PGP, RSA, etc. When
    - it comes time to rewrite this Sierra to support PGP/RSA we shouldn't have to
    - modify any of Sierra to support this.
    -
    - - need to provide an equals() method so that we can determine if two Ns are
    - the same.
    -
       - RSA authentication with public private key pairs and working signatures.
             - requires nym management.
     



    This archive was generated by hypermail 2b30 : Fri Feb 09 2001 - 14:39:12 PST