diff options
author | Bill Marquette <billm@pfsense.org> | 2005-03-04 16:47:47 +0000 |
---|---|---|
committer | Bill Marquette <billm@pfsense.org> | 2005-03-04 16:47:47 +0000 |
commit | 355229d0f3125699c6acd0c994da754af893ddfe (patch) | |
tree | e232118f3c5f6a755645866a063bfe541bcce1b7 | |
parent | 38560a2579ca902dfcf6a27f0f0ec2c59cf21972 (diff) | |
download | pfsense-355229d0f3125699c6acd0c994da754af893ddfe.zip pfsense-355229d0f3125699c6acd0c994da754af893ddfe.tar.gz |
typo
-rw-r--r-- | etc/inc/filter.inc | 2 | ||||
-rwxr-xr-x | usr/local/www/system_advanced.php | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/etc/inc/filter.inc b/etc/inc/filter.inc index 13b80be..b8d0fdc 100644 --- a/etc/inc/filter.inc +++ b/etc/inc/filter.inc @@ -996,7 +996,7 @@ EOD; $ipfrules .= <<<EOD # Fix sites that violate RFC 959 which specifies that the data connection -# be sourced from the command port - 1 (typicaly port 20) +# be sourced from the command port - 1 (typically port 20) # This workaround doesn't expose us to any extra risk as we'll still only allow # connections to the firewall on a port that ftp-proxy is listening on pass in quick on $wanif inet proto tcp from any to ($wanif) port > 49000 user proxy flags S/SA keep state label "FTP PROXY: RFC959 violation workaround" diff --git a/usr/local/www/system_advanced.php b/usr/local/www/system_advanced.php index 684047d..6be2631 100755 --- a/usr/local/www/system_advanced.php +++ b/usr/local/www/system_advanced.php @@ -321,7 +321,7 @@ function enable_change(enable_over) { <td width="22%" valign="top" class="vncell">FTP RFC 959 data port violation workaround</td> <td width="78%" class="vtable"> <input name="rfc959workaround" type="checkbox" id="rfc959workaround" value="yes" <?php if (isset($config['system']['rfc959workaround'])) echo "checked"; ?> onclick="enable_change(false)"> - <strong class="vexpl">Workaround for sites that violate RFC 959 which specifies that the data connection be sourced from the command port - 1 (typicaly port 20). This workaround doesn't expose you to any extra risk as the firewall will still only allow connections on a port that the ftp-proxy is listening on.</strong><br> + <strong class="vexpl">Workaround for sites that violate RFC 959 which specifies that the data connection be sourced from the command port - 1 (typically port 20). This workaround doesn't expose you to any extra risk as the firewall will still only allow connections on a port that the ftp-proxy is listening on.</strong><br> </tr> <tr> |