\chapter{Conclusion}

In this paper, we have seen a design for a service which encrypts data
in a key which it only knows.  This design allows the service to
provide an enforceable yet very flexible security system, since the
cryptographic system is used only to protect the data from being read;
the semantics of who may encrypt or decrypt data are decoupled from the
encryption mechanism.  This allows the Nox server to provide flexible
security semantics by using a generalized form of access control lists
to determine which principals are allowed to encrypt or decrypt data.
We have sketched out how several applications can be written or modified
to use the Nox server to provide their security.  Finally, we have
examined a few extensions to the basic design of the Nox server and some
directions for future work on Nox.

While the Nox server has not been implemented yet, it appears that it
will be extremely useful in providing security in a distributed
environment.


% 
% Local variables:
% version-control: t
% make-backup-files: t
% mode: TeX
% End:

