Mercurial > docs > diploma
comparison thesis/tex/4-MasqmailsFuture.tex @ 407:4b151c1b3835
remove obsolete comments plus tiny fixes
| author | meillo@marmaro.de |
|---|---|
| date | Sun, 08 Feb 2009 23:57:50 +0100 |
| parents | 1d527ad76c97 |
| children |
comparison
equal
deleted
inserted
replaced
| 406:1d527ad76c97 | 407:4b151c1b3835 |
|---|---|
| 645 | 645 |
| 646 Similar is the situation for security. Security comes from good design, explain \person{Graff} and \person{van Wyk}: | 646 Similar is the situation for security. Security comes from good design, explain \person{Graff} and \person{van Wyk}: |
| 647 | 647 |
| 648 \begin{quote} | 648 \begin{quote} |
| 649 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. | 649 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. |
| 650 % | |
| 651 %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. | |
| 652 \hfill\cite[page 55]{graff03} | 650 \hfill\cite[page 55]{graff03} |
| 653 \end{quote} | 651 \end{quote} |
| 654 \index{good design} | 652 \index{good design} |
| 655 | 653 |
| 656 They also suggest to add wrappers and interposition filters \emph{around} applications, but more as repair techniques if it is not possible to design security \emph{into} a software the first way \cite[pages~71--72]{graff03}. | 654 They also suggest to add wrappers and interposition filters \emph{around} applications, but more as repair techniques if it is not possible to design security \emph{into} a software the first way \cite[pages~71--72]{graff03}. |
| 721 | 719 |
| 722 Repair strategies are useful, but only in the short-time view and in times of trouble. If the future is bright, however, one does best by investing into a software. As shown in section~\ref{sec:market-analysis-conclusion}, the future for \MTA{}s is bright. This means it is time to invest into a redesign with the intention to build up a more modern product. | 720 Repair strategies are useful, but only in the short-time view and in times of trouble. If the future is bright, however, one does best by investing into a software. As shown in section~\ref{sec:market-analysis-conclusion}, the future for \MTA{}s is bright. This means it is time to invest into a redesign with the intention to build up a more modern product. |
| 723 | 721 |
| 724 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. | 722 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. |
| 725 \index{masqmail!new design} | 723 \index{masqmail!new design} |
| 726 | |
| 727 %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. | |
| 728 | 724 |
| 729 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. | 725 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. |
| 730 \index{quality improvement} | 726 \index{quality improvement} |
| 731 | 727 |
| 732 | 728 |