Virtualmin virtual-server module version 4.12 released

We're working on the "Perl dependent" problem. It's actually a big part of why it's taking so long. Theming Virtualmin is hard if you don't speak a lot of Perl and know the internals of Virtualmin very well (even though I'm OK with Perl, and know the internals of Virtualmin better than most folks other than Jamie, I'm still overwhelmed by it pretty frequently). We're almost there, thought. So much has gone on behind the scenes lately, and we're about to push a few more bits down into Virtualmin and out of the theme in the next revision or two, which will resolve quite a few of the difficulties in theming.

And, my goal with the Bootstrap theme I'm working on is that any Bootstrap theme that covers the components we use will apply directly and easily to our theme as an overlay. That's proving difficult with the left-hand menu (I'm torn between sticking with the default panel based accordion or using a custom menu that borrows from the Bootstrap defaults, possibly with a LESS template to automate that). i.e. no Perl needed, at all, for anything that doesn't fundamentally alter the structure of the UI. You may have seen the screenshots from a while back, where I applied a handful of WrapBootstrap themes to my theme; that was really simple. Just add the stylesheet, with no other customizations or tweaks.

It's happening! But, it's hard. We've got a 15+ year old code base that spans half a million lines of code. We're paying off some technical debt to make future development easier.

Try now. I may have forgotten to run the createrepo script after syncing. The package is definitely in the repo.

We remember, and we're grateful you've stuck with us all these years! And, yes, we're almost there. Virtualmin was founded in 2005.

2015 is gonna be a fantastic year for Virtualmin, Cloudmin, Webmin, and even little ol' Usermin. So many major developments are underway. I just spent the weekend at a Hackathon making a new module, doing more work on the new theme, improving the Webmin documentation wiki, and working on yet another new module. We plan to fork Webmin 2.0 (to allow incompatible changes in Webmin for the first time in its existence) early in 2015.

Have you tried fail2ban? It automatically inserts rules when someone attempts to login, but fails. There is a Webmin rule for fail2ban that is included in the package (also available here: https://github.com/fail2ban/fail2ban/blob/master/config/filter.d/webmin-... ), and a Webmin module for managing fail2ban, so it's pretty easy to get it running.

GeoIP is a cool idea, though I don't know of anyone who has built a Webmin authentication thingy for it. I might look into it. I've never written any authentication related code in Webmin, however, so it'd be new to me (and I suspect Jamie prefers the automated method provided by fail2ban).

You could also enable Two Factor Authentication. It won't prevent people from trying to log in, but it'll make it very hard for them to succeed.

I have looked at Ajenti briefly, and it looks really nice, though it's extremely limited compared to current Virtualmin and Webmin. Though it is developing at a nice clip. The first time I looked at it, it did almost nothing. Now it's got quite a few nice functions, and they seem to follow the Webmin philosophy of not screwing with existing configuration, which I like. So, perhaps they are a worthy competitor in the making. We've never really had one on the Webmin front (LinuxConf existed for a while, and was neat, but flawed), though Virtualmin has always had a lot of competition. They also seem to now be replicating our business model, which is interesting; they should have talked to me first...we aren't making enough money for anyone to want to replicate our business model!