extern/shorewall_code
1
0
Fork 1
mirror of https://gitlab.com/shorewall/code.git synced 2025-06-15 14:16:46 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge Simon's umask patch

Browse Source 
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@1937 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
This commit is contained in:
teastep 2005-02-02 17:58:10 +00:00
parent e0528c5555
commit 52aed7f6a5
4 changed files with 12 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Shorewall2/changelog.txt
View File

@ -1,7 +1,9 @@
Changes since 2.2.0 Changes in 2.2.1
1) Add examples to the zones and policy files. 1) Add examples to the zones and policy files.
2) Simon Matter's patch for umask.
Changes since 2.0.3 Changes since 2.0.3
1) Fix security vulnerability involving temporary files/directories. 1) Fix security vulnerability involving temporary files/directories.

3
Shorewall2/firewall
View File

@ -7065,6 +7065,9 @@ do_initialize() {
export LC_ALL=C export LC_ALL=C
# Make sure umask is sane
umask 177
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
# #
# Establish termination function # Establish termination function

6
Shorewall2/releasenotes.txt
View File

@ -5,6 +5,10 @@ Problems corrected in version 2.2.1
1) The /etc/shorewall/policy file contained a misleading comment and 1) The /etc/shorewall/policy file contained a misleading comment and
both that file and the /etc/shorewall/zones file lacked examples. both that file and the /etc/shorewall/zones file lacked examples.
2) Shorewall previously used root's default umask which could cause
files in /var/lib/shorewall to be world-readable. Shorewall now uses
umask 0177.
----------------------------------------------------------------------- -----------------------------------------------------------------------
Issues when migrating from Shorewall 2.0 to Shorewall 2.2: Issues when migrating from Shorewall 2.0 to Shorewall 2.2:
@ -88,7 +92,7 @@ Issues when migrating from Shorewall 2.0 to Shorewall 2.2:
OpenVPN. OpenVPN.
----------------------------------------------------------------------- -----------------------------------------------------------------------
New Features: New Features in Shorewall 2.2.0:
1) ICMP packets that are in the INVALID state are now dropped by the 1) ICMP packets that are in the INVALID state are now dropped by the
Reject and Drop default actions. They do so using the new Reject and Drop default actions. They do so using the new

2
Shorewall2/zones
View File

@ -11,7 +11,7 @@
# OVERLAPPING ZONES DEFINED THROUGH /etc/shorewall/hosts. # OVERLAPPING ZONES DEFINED THROUGH /etc/shorewall/hosts.
# #
# See http://www.shorewall.net/Documentation.htm#Nested # See http://www.shorewall.net/Documentation.htm#Nested
# #--------------------------------------------------------------------------------
# Example zones: # Example zones:
# #
# You have a three interface firewall with internet, local and DMZ interfaces. # You have a three interface firewall with internet, local and DMZ interfaces.