ufw should error if arguments given to "ufw enable"

[Dan Pritts]

Consider the following:

# ufw enable OpenSSH
Command may disrupt existing ssh connections. Proceed with operation (y|n)? y
Firewall is active and enabled on system startup

...but of course the OpenSSH application profile has not been loaded; the word "OpenSSH" was silently ignored.

It is (IMO) a reasonable user error - the syntax "sounds" like it should work. And the warning message is a great red herring, sigh.

So, I believe that ufw should check to see if there are other arguments specified after single-argument commands, and throw an error.

behavior verified on ubuntu 12.04 Version: 0.31.1-1; i took a quick look at the ufw release notes and it does not seem this is addressed in any subsequent releases.

thanks!

[Jamie Strandboge (jdstrand)]

This was fixed in 0.35.