openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

Revisions of shorewall

Bruno Friedmann (bruno_friedmann) accepted request 509826 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 229)

- bugfix release 5.1.4.4
  A defect in 5.1.4.3 caused a startup failure when two or more
  'fallback' providers were configured. That has been corrected. 
- Should be pushed also for 42.3

buildservice-autocommit accepted request 507225 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 228)

baserev update by copy to link target

Bruno Friedmann (bruno_friedmann) accepted request 507102 from

Antonio Larrosa (alarrosa) over 7 years ago (revision 227)

- Fix a typo in %posttrans that would remove the wrong file and could
  cause a problem depending on the execution order of the %pretrans
  and %posttrans scripts for the shorewall and shorewall6 packages.

Bruno Friedmann (bruno_friedmann) accepted request 505369 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 226)

- This stable branch 5.1x will be the new default for Leap 42.3.
  Remember that each time you have an upgrade with changes in Major
  or Major,Minor it is mandatory you upgrade your configuration 
  with shorewall(6) update -a /etc/shorewall(6) command.
- Packaging : use pretrans and posttrans to inform user about 
  configuration upgrade.
- Bugfix release 5.1.4.3. Problem Corrected:
  When running on prior-generation distributions such as RHEL6,
  IPv6 multi-ISP configurations failed to start due to an error 
  such as the following:
   ERROR: Command "ip -6 -6 route replace default scope global
          table 250 nexthop via ::192.88.99.1 dev tun6to4 weight 1"
          Failed
  Such configurations now start successfully.

buildservice-autocommit accepted request 504332 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 225)

baserev update by copy to link target

Bruno Friedmann (bruno_friedmann) accepted request 503677 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 224)

- Bugfix and enhancement release 5.1.4.2
  complete changelog is available
  http://shorewall.net/pub/shorewall/5.1/shorewall-5.1.4/releasenotes.txt
- Main changes
  All IPv6 standard actions have been deleted and their logic
  has been added to their IPv4 counterparts who can now handle
  both address families.
  Previously, ?error and ?require messages as well as verbose ?info
  and ?warning messages (those that report the file and line numbers)
  generated from an action file would report the action file name and
  line number rather than the file and line number where the action
  was invoked. The file and line number where the action was invoked
  were listed second. Beginning with this release, the invoking file
  and line number are listed first and the action file and line number
  are not reported. This allows for creation of clearer messages.
  
  IPv6 UPnP support (including MINIUPNPD) is now available.
  A PERL_HASH_SEED option has been added to allow the Perl hash seed
  to be specified.  See shorewall.conf(5) and perlsec(1) for details.

buildservice-autocommit accepted request 482804 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 223)

baserev update by copy to link target

Bruno Friedmann (bruno_friedmann) accepted request 482666 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 222)

- Bugfix release 5.1.3.2
  Previously, if a Shorewall Variable (e.g., @chain) was the target
  of a conditional ?RESET directive (one that was enclosed in ?if.
  ?else...?endif logic), the compiler could incorrectly use an
  existing chain created from the action rather than creating a new
  (and different) chain. That has been corrected.
  Previously, if alternate input format specified a column that had
  already been specified, the contents of that column were silently
  overwritten. Now, a warning message is issued stating that the
  prior value has been replaced by the newer value.

Bruno Friedmann (bruno_friedmann) committed over 7 years ago (revision 221)

buildservice-autocommit accepted request 481217 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 220)

baserev update by copy to link target

Bruno Friedmann (bruno_friedmann) committed over 7 years ago (revision 219)

update to bugfix 5.1.3.1

Bruno Friedmann (bruno_friedmann) committed over 7 years ago (revision 218)

buildservice-autocommit accepted request 479770 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 217)

baserev update by copy to link target

Bruno Friedmann (bruno_friedmann) accepted request 479769 from

Bruno Friedmann (bruno_friedmann) over 7 years ago (revision 216)

- Upgrade to last stable 5.1.3 
  For details see changelog.txt and releasenotes.txt containing all
  informations for a correct upgrade path.
- Packaging Redone patches for var-fillup
  + shorewall-fillup-install.patch
  + shorewall-init-fillup-install.patch
  + shorewall-lite-fillup-install.patch

- Upgrade to stable 5.1.1 
  For details see changelog.txt and releasenotes.txt containing all
  informations for a correct upgrade path.
- Packaging:
  + use proper %{} syntax
  + Adjust year copyright
  + Remove attr on sbindir symlink
  + Move Samples and Contrib to doc package

buildservice-autocommit accepted request 447292 from

Bruno Friedmann (bruno_friedmann) almost 8 years ago (revision 215)

baserev update by copy to link target

Bruno Friedmann (bruno_friedmann) accepted request 445338 from

Bruno Friedmann (bruno_friedmann) almost 8 years ago (revision 214)

- Upgrade to last stable of 5.0.x version 5.0.15
  For details see changelog.txt and releasenotes.txt containing all
  informations for a correct upgrade path.
- Packaging :
  + Remove all non suse %if 
  + Cleanup older non supported version
  + Remove upstream merged patch
    * 0001-remote_fs.patch
    * 0001-required-stop-fix.patch
  + Remove 0001-fillup-install.patch replaced by specific product
    patch for correct usage of var-fillup
  + Added patches for var-fillup when not specific %name6 is also
    supported
    * shorewall-fillup-install.patch
    * shorewall-init-fillup-install.patch
    * shorewall-lite-fillup-install.patch
  + spec-cleaner minimal

buildservice-autocommit accepted request 371244 from

Jan Engelhardt (jengelh) over 8 years ago (revision 213)

baserev update by copy to link target

Jan Engelhardt (jengelh) accepted request 367131 from

Bruno Friedmann (bruno_friedmann) over 8 years ago (revision 212)

Update to last bugfix 4.x series 
Thanks for your consideration.
Maintainer status is accepted since togan has disappear
Will serve as maintenance sr for Leap + Factory submission

buildservice-autocommit accepted request 331030 from

Togan Muftuoglu (toganm) about 9 years ago (revision 211)

baserev update by copy to link target

Togan Muftuoglu (toganm) accepted request 331029 from

Togan Muftuoglu (toganm) about 9 years ago (revision 210)

- Update to version 4.6.13 For more details see changelog.txt and
  realeasenotes.txt
  * The 'rules' file manpages have been corrected regarding the
    packets that are processed by rules in the NEW section.
  * Parsing of IPv6 address ranges has been corrected. Previously,
    use of ranges resulted in 'Invalid IPv6 Address' errors.
  * The shorewall6-hosts man page has been corrected to show the
    proper contents of the HOST(S) column.
  * Previously, INLINE statements in the mangle file were not 
    recognized if a chain designator (:F, :P, etc.) followingowed 
    INLINE(...). As a consequence, additional matches following
    a semicolon were interpreted as column/value pairs unless
    INLINE_MATCHES=Yes, resulting in compilation failure.
  * Inline matches on IP[6]TABLE rules could be ignored if
    INLINE_MATCHES=No. They are now recognized.
  * Specifying an action with a logging level in one of the
    _DEFAULT options in shorewall[6].conf
    (e.g., REJECT_DEFAULT=Reject:info) produced a compilation error:
      ERROR: Invalid value (:info) for first Reject parameter
           /usr/share/shorewall/action.Rejectect (line 52)
    That has been corrected. Note, however, that specifying logging
    with a default action tends to defeat one of the main purposes
    of default actions which is to suppress logging.
  * Previously, it was necessary to set TC_EXPERT=Yes to have full
    access to the user mark in fw marks. That has been corrected so
    that any place that a mark or mask can be specified, both the
    TC mark and the User mark are accessible.

Displaying revisions 61 - 80 of 289

Places

Revisions of shorewall

Places