If you are doing an interactive install (no AUTOPILOT) via remote ssh, the step of installing CSF (firewall) may break the process, locking out the user.

I don't know if it happened to me because csf started or because in the csf_install() function there is a "ssh restart", but I've been disconnected and script didn't finish correctly (because it still had to ask questions later...)

There are many other situations in which an incomplete csf configuration (no whitelisted IPs) can lockout users (e.g. temp ban).

It could be better to activate csf only as a final step, when everything else is already well configured... or you have to start again from scratch or finish Barracuda setup by hand, step-by-step!

(Yes, I know you should always use console or 'screen' tool when doing setup things like that...)

Anyway, keep up the (always improving) good job!

Comments

omega8cc’s picture

omega8cc commented

It could be improved, for sure and we can of course move it to the end of the install process. That is a good idea.

Note however, that by default CSF does add your IP to the whitelist, so you should never be locked out. Also, even if you have dynamic IP and it will change during the install, still there is no reason to be locked out, unless you are trying to run port scan or something like that in the meantime.

That said, I would be interested to hear more details on how to get locked out during install, since I can't reproduce the issue.

omega8cc’s picture

omega8cc commented
Status: Active » Fixed

Fixed in commit: http://drupalcode.org/project/barracuda.git/commit/b69d5fe

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.