1.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Sun Feb 08 23:51:48 2009 +0100
     1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Sun Feb 08 23:57:50 2009 +0100
     1.3 @@ -647,8 +647,6 @@
     1.4  
     1.5  \begin{quote}
     1.6  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 maintenance of the software.
     1.7 -%
     1.8 -%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.9  \hfill\cite[page 55]{graff03}
    1.10  \end{quote}
    1.11  \index{good design}
    1.12 @@ -724,8 +722,6 @@
    1.13  In the author's view is \masqmail\ already needing this redesign since about 2003 when the old design was still quite suitable \dots\ it already delayed too long.
    1.14  \index{masqmail!new design}
    1.15  
    1.16 -%Clinging to much to existing code will be no help, it is an indicator for fear. Having the courage to through bad code away to make it better, shows the view forward.
    1.17 -
    1.18  Anyway, further development on base of current code needs to improve the quality properties, too. Some quality requirements can be satisfied by adding wrappers or interposition filters to the outside. For those is the development effort approximately equal to a solution with a new design. But for adding quality requirements like extendability or maintainability which affect the source code throughout, the effort does increase with exponential rate as development proceeds. In case these properties get not improved, development will likely come to a dead end sooner or later.
    1.19  \index{quality improvement}
    1.20