Hmmm, I knew that I'm not the only one who wants a "Webmin done right". It should ...

• be really paranoid about all data coming from the network
• survive a perl upgrade, both by an automatic system update and by a "cutting-edge-admin"
• work with old perl versions (think "Debian oldstable", i.e. 5.8.8, or even older)
• have few external requirements (don't require Oracle 11i just to store sessions, don't require half of CPAN)
• be pure perl
• bring its own web server
• be able to use PAM for authentication and authorisation
• work with all, or at least most Linux distributions, the *BSDs, Solaris, and whatever looks roughly like a Unix, even if it was relased five years ago
• be modular, allowing to add plugins for my microwave oven and my server room laser defense system
• be fast and lightweight. Webmins image-based headlines just SUCK!
• not require Javascript, Java, Flash or other Plugins. Using those features to ENHANCE the interface is ok, but the basic interface should be plain (and valid) HTML or XHTML. Some plugins may be excepted from this rule, like an SSH oder VNC client in a Java-Applet.

The interface should ALWAYS run as unprivileged user. A small, separate process should do the privileged work, and that process should not communicate with the browser. And that process is not invoked via the shell, but directly (i.e. NO system "command and parameters"), just to avoid nasty shell surprises.

Alexander