\documentclass[11pt]{article}


\title{ MIT Crypto Card, Progress Presentation }
\author{Chris Laas}
\date{November 30, 2000}

%\pagestyle{myheadings}
%\markright{Chris Laas \hfil }





\def\H{\mathcal{H}}

\def\Sign{\mbox{\it Sign}}
\def\Verify{\mbox{\it Verify}}
\def\Decrypt{\mbox{\it Decrypt}}
\def\Encrypt{\mbox{\it Encrypt}}


\usepackage{amsmath}
\usepackage{amsfonts}
\DeclareMathSymbol{\Z}{\mathalpha}{AMSb}{"5A}
\def\Zp{\Z_p}
\def\Zps{\Zp^*}
\def\Zq{\Z_q}
\def\Zqs{\Zq^*}
\def\Zn{\Z_n}
\def\Zns{\Zn^*}
\def\inr{\in_\mathcal{R}}


% What a hack.  LaTeX... sucks!
\def\cpt#1{
\vskip 0.5em
\begin{tabular}{|l|}\hline
{\bf
%    Design Counterpoint:
                          #1} \\
\begin{minipage}{29em}
\vspace{0.25em}
}
\def\endcpt{
\vspace{0.25em}
\end{minipage} \\ \hline
\end{tabular}
\vskip 0.5em
}






\begin{document}
\maketitle

{\center \small
 \verb|$Id: handout.tex,v 1.1 2000/11/30 23:19:36 golem Exp $|}



\section{Purpose of the project}
\begin{itemize}
\item
  The MIT Crypto Card project will develop a successor to the MIT Card
  which, using modern cryptographic techniques which were not
  available to the designers of the original MIT Card, will provide
  authorization functionality to the MIT campus without compromising
  the security or privacy of the card users.
\item
  The new Card will serve as identification, authorize access to
  reader-equipped doors on campus, and mediate small "pocket change"
  cash transfers.
\item
  The system will include the following elements:
  \begin{itemize}
  \item
    Microcontroller-based portable "MIT Card" tokens.
  \item
    A set of trusted authentication servers, or CAs (Certificate
    Authorities).
  \item
    A network of vendor terminals, authentication terminals, and
    interface terminals.
  \end{itemize}
\end{itemize}




\section{What we've done so far}
\begin{itemize}
\item
  Literature review (CAFE, secure cash, group identification protocols)
\item
  Extensive documentation of system requirements:
  \begin{itemize}
  \item
    Identification, group authorization, pocket change, administration
  \item
    Scaling requirements
  \item
    Management and administration --- decentralization of control,
    data quality, data privacy policies
  \end{itemize}
\item
  Evaluated hardware:
  \begin{itemize}
  \item
    Several smart cards (e.g. Gemplus): the market is rather homogeneous.
  \item
    iKey:  advantage is form factor, compatibility, and LED;
    disadvantage is reliability (sturdiness)
  \item
    Gemplus CAFE token:  Gemplus never turned them into a real product,
    but perhaps could be convinced to make a new prototype.
  \item
    PDAs:  Still too expensive.  Give it a few years?
  \end{itemize}
\item
  Protocol and system design:
  \begin{itemize}
  \item
    Identification protocols
    \begin{itemize}
    \item
      Researched options; will take one that works "out of the box."
    \item
      Fiat-Shamir is current default.
    \item
      Modular "pluggable" part of system.
    \end{itemize}
  \item
    Cash protocols
    \begin{itemize}
    \item
      Researched options; there is a great variety.
    \item
      Will choose a conservative, but flexible design.
    \item
      This module is a low priority --- authentication comes first.
    \end{itemize}
  \item
    Group authorization protocols
    \begin{itemize}
    \item
      Researched existing protocols --- none provide anonymity and revocation.
    \item
      Designed a new system and set of protocols.
      \begin{itemize}
      \item
        Heavily based on Ohta, Okamoto, and Koyama's system [OOK90],
        which is heavily based on Chick and Tavares's system [CT89].
        A few minor changes to support anonymity were made, and a
        system to provide revocation functionality was built on top of it.
      \item
        Security rests on the RSA assumption.
      \end{itemize}
    \end{itemize}
  \item
    CA and key management protocols
    \begin{itemize}
    \item
      Resilient and simple certificate management hierarchy, based on
      standard models.
    \end{itemize}
  \end{itemize}
\item
  Results of independent interest:
  \begin{itemize}
  \item
    New privacy-preserving practical group authorization protocols.
  \item
    Formulation of the problem of "identity escrow".
  \end{itemize}
\end{itemize}


\section{Plans for the immediate future}
\begin{itemize}
\item
  Hire someone!  Talent with free time is hard to find and retain.
\item
  IAP:  Concretize the protocols in preparation for review.
\item
  End of IAP:  Submit protocols for review.
\item
  Spring:  Begin software prototypes.
\item
  {\bf Where have the plans changed?}
  \begin{itemize}
  \item
    We are taking a much more conservative view of hardware than we
    initially envisioned.  Given budget constraints, we will have to
    work with some primarily off-the-shelf system; this also means
    that the technology we will have available is less predictable.
    Hence, the protocols we design have more of an emphasis on
    technology agnosticism.  In addition, there is more of an emphasis
    on flexibility, as we cannot predict what will be the best
    platform options in a decade.
  \end{itemize}
\end{itemize}



\section{Long term plans}
\begin{itemize}
\item
  Hire someone!
  \begin{itemize}
  \item
    In general, increase the size of the core group.  Must find
    good systems programmers and good network programmers.
  \item
    Also, work on increasing the budget.  Budget will have a direct
    effect on ability to hire talent.
  \end{itemize}
\item
  Technical plans
  \begin{itemize}
  \item
    (ongoing) Keep an eye on hardware developments.
    \begin{itemize}
    \item
      consider likely technology developments: e.g. pan-campus
      wireless Ethernet coverage, advanced PDAs, more embedded computation.
    \end{itemize}
  \item
    Finish software prototypes.
  \item
    Audit software.
  \item
    Port software to hardware embodiments.
  \item
    Set up a demo cluster.
  \end{itemize}
\item
  Documentation
  \begin{itemize}
  \item
    Write design documentation, technical specs, and manuals for the
    modules of the system.
  \item
    Document operations of the system, including contingency plans.
  \end{itemize}
\end{itemize}





\end{document}
