[pve-devel] applied: [PATCH firewall v2] fix #2004: do not allow backwards ranges

Wolfgang Bumiller w.bumiller at proxmox.com
Mon Dec 3 14:12:17 CET 2018


applied

On Fri, Nov 30, 2018 at 04:31:41PM +0100, Dominik Csapak wrote:
> ranges like 10:5 are allowed by us, but iptables throws an error
> that is only visible in the syslog and the firewall rules do not
> get updated
> 
> Signed-off-by: Dominik Csapak <d.csapak at proxmox.com>
> ---
> changes from v1:
> * better error message
>  src/PVE/Firewall.pm | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/src/PVE/Firewall.pm b/src/PVE/Firewall.pm
> index 035dc7e..db1eae3 100644
> --- a/src/PVE/Firewall.pm
> +++ b/src/PVE/Firewall.pm
> @@ -1054,6 +1054,7 @@ sub parse_port_name_number_or_range {
>  	    my ($port1, $port2) = ($1, $2);
>  	    die "invalid port '$port1'\n" if $port1 > 65535;
>  	    die "invalid port '$port2'\n" if $port2 > 65535;
> +	    die "backwards range '$port1:$port2' not allowed, did you mean '$port2:$port1'?\n" if $port1 > $port2;
>  	} elsif ($item =~ m/^([0-9]+)$/) {
>  	    $count += 1;
>  	    my $port = $1;
> -- 
> 2.11.0




More information about the pve-devel mailing list