bad rule interpretation

[Hans Ginzel]

It seems that ufw from rule
[Rule1]
ufw_rule = 22/tcp ALLOW IN Anywhere
description = SSH
command = ufw allow in 22/tcp
policy = allow
direction = in
protocol =
from_ip = 10.0.0.0/28
from_port =
to_ip =
to_port = 22/tcp
iface =
logging =

produces

Appending new Gufw rule: ufw allow in from 10.0.0.0/28 22/tcp > ERROR: Wrong number of arguments

instead of

ufw allow in from 10.0.0.0/28 port 22 proto tcp
.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: gufw 13.10.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-15.8-lowlatency 3.11.10
Uname: Linux 3.11.0-15-lowlatency i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Fri Jan 31 18:46:38 2014
EcryptfsInUse: Yes
MarkForUpload: True
PackageArchitecture: all
SourcePackage: gui-ufw
UpgradeStatus: Upgraded to saucy on 2013-10-24 (99 days ago)

[costales (costales)]

I'll review this :) There're dragons in that point of code :S hehehe

[Hans Ginzel (hans-matfyz)]

I hope I found one of the dragon. Be inspired by attached patch.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "corrected ufw command" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[costales (costales)]

Uhm... Could you try the last version please? :) (It works in Ubuntu 13.10):
sudo apt-get purge gufw ; sudo rm -r /etc/gufw ; wget https://launchpad.net/gui-ufw/gufw-14.04/14.04/+download/gufw_14.04.1.deb ; sudo dpkg -i gufw_14.04.1.deb

As you can see in the attachment screenshots:
 1. User enters port 22 and he can set the protocol in the combobox Protocol.
 2. User enters port 22/tcp and some fields will be disabled (as IP).

As I told you, there are dragons there :P I just don't remember the case, but ufw was not allowing a specific command and then I preferred to guarantee the user's entry enabling/disabling fields and ensure that any command will be right.

The current Gufw is a LTS, then I'm so sorry, but I'll not change this behaviour now :S But I'll think in your proposal either! ;)