extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-24 19:51:40 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix Makefile's entry in the .spec file

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@3733 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2006-03-25 15:44:48 +00:00
parent 4f7022b960
commit 3e05dab080
2 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Shorewall/releasenotes.txt
View File

@ -32,13 +32,17 @@ Problems Corrected in 3.2.0 Beta 3
1) The 'try' command with an effective verbosity of zero resulted in an 1) The 'try' command with an effective verbosity of zero resulted in an
error message and the command failed. error message and the command failed.
2) /etc/shorwall/Makefile was incorrectly described as %config(noreplace)
in the RPM .spec file. This prevented updated versions of the file
from being installed properly.
Other changes in 3.2.0 Beta 2 Other changes in 3.2.0 Beta 2
2) A new IMPLICIT_CONTINUE option has been added to shorewall.conf. When 2) A new IMPLICIT_CONTINUE option has been added to shorewall.conf. When
this option is set to "Yes", it causes subzones to be treated differently this option is set to "Yes", it causes subzones to be treated differently
with respect to policies. with respect to policies.
Subzones are defined by following their name by ":" and a list of parent Subzones are defined by following their name with ":" and a list of parent
zones (in /etc/shorewall/zones). Normally, you want to have a set of zones (in /etc/shorewall/zones). Normally, you want to have a set of
special rules for the subzone and if a connection doesn't match any of special rules for the subzone and if a connection doesn't match any of
those subzone-specific rules then you want the parent zone rules to be those subzone-specific rules then you want the parent zone rules to be
@ -58,7 +62,7 @@ Other changes in 3.2.0 Beta 2
par ipv4 par ipv4
chld:par ipv4 chld:par ipv4
And traffic to/from the 'chld' zone will first pass through the applicable Traffic to/from the 'chld' zone will first pass through the applicable
'chld' rules and if none of those rules match then it will be passed through 'chld' rules and if none of those rules match then it will be passed through
the appropriate 'par' rules. If the connection request does not match the appropriate 'par' rules. If the connection request does not match
any of the 'par' rules then the relevant 'par' policy is applied. any of the 'par' rules then the relevant 'par' policy is applied.

4
Shorewall/shorewall.spec
View File

@ -99,7 +99,7 @@ fi
%attr(0600,root,root) %config(noreplace) /etc/shorewall/providers %attr(0600,root,root) %config(noreplace) /etc/shorewall/providers
%attr(0600,root,root) %config(noreplace) /etc/shorewall/tcclasses %attr(0600,root,root) %config(noreplace) /etc/shorewall/tcclasses
%attr(0600,root,root) %config(noreplace) /etc/shorewall/tcdevices %attr(0600,root,root) %config(noreplace) /etc/shorewall/tcdevices
%attr(0600,root,root) %config(noreplace) /etc/shorewall/Makefile %attr(0600,root,root) /etc/shorewall/Makefile
%attr(05555,root,root) /sbin/shorewall %attr(05555,root,root) /sbin/shorewall
@ -179,6 +179,8 @@ fi
%doc COPYING INSTALL changelog.txt releasenotes.txt tunnel ipsecvpn Samples %doc COPYING INSTALL changelog.txt releasenotes.txt tunnel ipsecvpn Samples
%changelog %changelog
* Sat Mar 25 2006 Tom Eastep tom@shorewall.net
- Remove '%config' from Makefile
* Thu Mar 23 2006 Tom Eastep tom@shorewall.net * Thu Mar 23 2006 Tom Eastep tom@shorewall.net
- Updated to 3.2.0-0Beta2 - Updated to 3.2.0-0Beta2
* Thu Mar 09 2006 Tom Eastep tom@shorewall.net * Thu Mar 09 2006 Tom Eastep tom@shorewall.net