1993-02-10 - Crypto goals

Header Data

From: Marc.Ringuette@GS80.SP.CS.CMU.EDU
To: cypherpunks@toad.com
Message Hash: 5520620b381fef24ec82e1c81915e858f3b704ed289140b4d5616f76bfc305b4
Message ID: <9302102256.AA29342@toad.com>
Reply To: N/A
UTC Datetime: 1993-02-10 22:56:23 UTC
Raw Date: Wed, 10 Feb 93 14:56:23 PST

Raw message

From: Marc.Ringuette@GS80.SP.CS.CMU.EDU
Date: Wed, 10 Feb 93 14:56:23 PST
To: cypherpunks@toad.com
Subject: Crypto goals
Message-ID: <9302102256.AA29342@toad.com>
MIME-Version: 1.0
Content-Type: text/plain


Y'know, just defining "what we should want" is one of the biggest
challenges in moving towards the next generation of crypto.  How
about making a list of features we want, and/or a list of scenarios
we want to be able to handle?

Uncontroversial features:
    message privacy
    message anonymity
    message untraceability
    digital cash
    digital time stamps

More difficult/controversial features:
    message invisibility [e.g. in low bits of video signal]
    untraceable access to databases [just anonymous email?]
    electronic black markets [just electronic cash and anonymous email?]
    electronic voting
    m-of-n trust schemes
    time-delay messages [are they useful?]
    executable but non-disassemblable code [is it possible?]
    tagging / un-tagging of copyrighted text [what is possible?]
       [explanation to follow in another message ]

I know how to take a crack at implementing all of these except the last
two, but would benefit from better theoretical and practical work on
all of them.  Most of them are obviously useful, and scenarios come
easily to mind.  

Have I missed anything?


-- Marc Ringuette (mnr@cs.cmu.edu)





Thread