Shoreline Firewall is an iptables-based firewall for Linux systems
The Shoreline Firewall, more commonly known as "Shorewall", is a Netfilter
(iptables) based firewall that can be used on a dedicated firewall system,
a multi-function gateway/ router/server or on a standalone GNU/Linux system.
- Developed at security:netfilter
- Sources inherited from project openSUSE:Factory
-
2
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout openSUSE:Factory:Rebuild/shorewall && cd $_
- Create Badge
Refresh
Refresh
Source Files
Filename | Size | Changed |
---|---|---|
0001-fillup-install.patch | 0000001102 1.08 KB | |
0001-remote_fs.patch | 0000000548 548 Bytes | |
0001-required-stop-fix.patch | 0000000617 617 Bytes | |
README.openSUSE | 0000000879 879 Bytes | |
shorewall-4.4.22.rpmlintrc | 0000000682 682 Bytes | |
shorewall-4.6.6.1.tar.bz2 | 0000485418 474 KB | |
shorewall-core-4.6.6.1.tar.bz2 | 0000053900 52.6 KB | |
shorewall-docs-html-4.6.6.1.tar.bz2 | 0004179739 3.99 MB | |
shorewall-init-4.6.6.1.tar.bz2 | 0000034261 33.5 KB | |
shorewall-lite-4.6.6.1.tar.bz2 | 0000048299 47.2 KB | |
shorewall.changes | 0000105174 103 KB | |
shorewall.spec | 0000025348 24.8 KB | |
shorewall6-4.6.6.1.tar.bz2 | 0000225573 220 KB | |
shorewall6-lite-4.6.6.1.tar.bz2 | 0000047753 46.6 KB |
Revision 82 (latest revision is 125)
Dominique Leuenberger (dimstar_suse)
accepted
request 282634
from
Togan Muftuoglu (toganm)
(revision 82)
- Update to version 4.6.6.1 For more details see changelog.txt and releasenotes.txt * Previously the SAVE and RESTORE actions were erroneously disallowed in the INPUT chain within the mangle file. * The manpage descriptions of the mangle SAVE and RESTORE actions incorrectly required a slash (/) prior to the mask value. * Race conditions could previously occur between the 'start' command and the 'enable' and 'disable' commands. * The 'update' command incorrectly added the INLINE_MATCHES option to shorewall.conf with a default value of 'Yes'. This caused 'start' to fail with invalid iptables rules when the alternate input format using ';' is used. * Previously the LOCKFILE setting was not propagated to the generated script. So when the script was run directly, the script unconditionally used ${VARDIR}/lock. (forwarded request 282633 from toganm)
Comments 0