A few months ago, I wrote httpdito, a tiny web server that serves static pages only. It's about the same amount of code as nweb, but less functionality, and I have more confidence in its security: <a href="http://canonical.org/~kragen/sw/dev3/server.s" rel="nofollow">http://canonical.org/~kragen/sw/dev3/server.s</a>, with README at <a href="http://canonical.org/~kragen/sw/dev3/httpdito-readme" rel="nofollow">http://canonical.org/~kragen/sw/dev3/httpdito-readme</a>. It's 296 instructions.<p>I'm not saying it's secure, but I certainly intended it to be, and it doesn't suffer from the particular problems tptacek, evmar, kedean, and nknighthb identify in nweb. I'd like to think I'm not naïve enough to have written problems like that, but that's probably not true.<p>(I'm pretty sure that "Try my new secure software!" is something that should not be followed with "I wrote it in C!" but usually assembly language is not going to be an improvement. In this case I think it happens to be.)<p>httpdito was discussed on HN a bit before it was finished; for example, it's no longer completely trivial to DoS it, although I could do more to protect it against that.