1.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Sun Jan 04 22:36:53 2009 +0100
     1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Sun Jan 04 22:57:49 2009 +0100
     1.3 @@ -47,6 +47,8 @@
     1.4  
     1.5  This section identifies the requirements for a modern \masqmail. Most of them will apply to modern \MTA{}s in general.
     1.6  
     1.7 +%Now that it is explained why email will survive (in some changed but related form), it is time to think about the properties required for \mta{}s in the next years. Because as the fields and kinds of usage change, the requirement change too.
     1.8 +
     1.9  
    1.10  
    1.11  \subsection{General requirements}
    1.12 @@ -318,7 +320,8 @@
    1.13  
    1.14  \person{Hafiz} agrees: ``The goal of making software secure can be better achieved by making the design simple and easier to understand and verify.''\cite[page 64]{hafiz05} He identifies the security of \qmail\ to come from it's \name{compartmentalization}, which goes hand in hand with modularity:
    1.15  \begin{quote}
    1.16 -A perfect example is the contrast between the feature envy early \sendmail\ architecture implemented as one process and the simple, modular architecture of \qmail. The security of \qmail\ comes from its compartmentalized simple processes that perform one task only and are therefore testable for security. \cite[page 64]{hafiz05}
    1.17 +A perfect example is the contrast between the feature envy early \sendmail\ architecture implemented as one process and the simple, modular architecture of \qmail. The security of \qmail\ comes from its compartmentalized simple processes that perform one task only and are therefore testable for security.
    1.18 +\hfill\cite[page 64]{hafiz05}
    1.19  \end{quote}
    1.20  As well does \person{Dent} for \postfix: ``The modular architecture of Postfix forms the basis for much of its security.'' \cite[page 7]{dent04}
    1.21  
    1.22 @@ -329,7 +332,7 @@
    1.23  Good design is the sword and shield of the security-conscious developer. Sound design defends your application from subversion or misuse, protecting your network and the information on it from internal and external attacks alike. It also provides a safe foundation for future extensions and maintainance of the software.
    1.24  %
    1.25  %Bad design makes life easier for attackers and harder for the good guys, especially if it contributes to a false sends of security while obscuring pertinent failings.
    1.26 -\cite[page 55]{graff03}
    1.27 +\hfill\cite[page 55]{graff03}
    1.28  \end{quote}
    1.29  
    1.30