Mercurial > docs > diploma

comparison thesis/tex/4-MasqmailsFuture.tex @ 218:711f0d3f5dfd

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
minor change for block quotes
author meillo@marmaro.de
date Sun, 04 Jan 2009 22:57:49 +0100
parents f2b8481789f6
children 5adc26977dc6
comparison
equal deleted inserted replaced
217:d645ac015c3b 218:711f0d3f5dfd
44 44
45 45
46 \section{Requirements} 46 \section{Requirements}
47 47
48 This section identifies the requirements for a modern \masqmail. Most of them will apply to modern \MTA{}s in general. 48 This section identifies the requirements for a modern \masqmail. Most of them will apply to modern \MTA{}s in general.
49
50 %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.
49 51
50 52
51 53
52 \subsection{General requirements} 54 \subsection{General requirements}
53 55
316 318
317 Every one of the popular \MTA{}s is more modular, or became more modular over time, than \masqmail\ is. Modern requirements like spam protection and future requirements like---probably---the use of new mail transport protocols demand modular designs for keeping the software simple. Simplicity is a key property for security. ``[T]he essence of security engenieering is to build systems that are as simple as possible.''\cite[page 45]{graff03} 319 Every one of the popular \MTA{}s is more modular, or became more modular over time, than \masqmail\ is. Modern requirements like spam protection and future requirements like---probably---the use of new mail transport protocols demand modular designs for keeping the software simple. Simplicity is a key property for security. ``[T]he essence of security engenieering is to build systems that are as simple as possible.''\cite[page 45]{graff03}
318 320
319 \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: 321 \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:
320 \begin{quote} 322 \begin{quote}
321 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} 323 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.
324 \hfill\cite[page 64]{hafiz05}
322 \end{quote} 325 \end{quote}
323 As well does \person{Dent} for \postfix: ``The modular architecture of Postfix forms the basis for much of its security.'' \cite[page 7]{dent04} 326 As well does \person{Dent} for \postfix: ``The modular architecture of Postfix forms the basis for much of its security.'' \cite[page 7]{dent04}
324 327
325 Modularity is also needed to satisfy modern \MTA\ requirements, in providing a clear interface to add functionality without increasing the overall complexity much. 328 Modularity is also needed to satisfy modern \MTA\ requirements, in providing a clear interface to add functionality without increasing the overall complexity much.
326 329
327 Security comes from good design, as \person{Graff} and \person{van Wyk} explain: 330 Security comes from good design, as \person{Graff} and \person{van Wyk} explain:
328 \begin{quote} 331 \begin{quote}
329 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. 332 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.
330 % 333 %
331 %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. 334 %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.
332 \cite[page 55]{graff03} 335 \hfill\cite[page 55]{graff03}
333 \end{quote} 336 \end{quote}
334 337
335 338
336 All this leads to the wish of a rewrite of \masqmail, using a modern, modular architecture, \emph{if} further features need to be added---ones that require changes in \masqmail's structure. But a rewrite is also needed, if \masqmail\ should become a modern \MTA, with good quality properties. 339 All this leads to the wish of a rewrite of \masqmail, using a modern, modular architecture, \emph{if} further features need to be added---ones that require changes in \masqmail's structure. But a rewrite is also needed, if \masqmail\ should become a modern \MTA, with good quality properties.
337 340