similar to: RE: [Shorewall-users] Web CVS Interface Currently Unavailable

I''ve removed the link from the index to the CVS WEB interface until I can figure out how to stop the %$#@s who are running HTTrack, WebStripper, etc. against it. In the mean time, all sites having in-progress sessions using these tools have been blacklisted. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \

On Sat, 15 Jun 2002, Ron Shannon wrote: > > I am ready to begin the documentation changes for 1.3.2. Are > > you close to > > having any of your changes ready for release? If so, we can > > get those into > > CVS before I begin my changes -- if not, then I''ll go ahead > > and update CVS > > with the 1.3.2 material. > > > >

There is now a link from the Shorewall home page to the CVS repository. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

I''ve created a repository at mail.shorewall.net:/usr/local/cvs. The Shorewall Website/Documentation is in a Project called Shorewall-docs. If you would like access to the repository, send me: a) The IP address that you will be accessing the repository from. b) A user name that you want to use to access the repository. c) Your password encrypted as described at

The volume of traffic at here at shorewall.net has reached the point where response time is beginning to suffer. I have therefore decided to move the main web site back to SourceForge at http://shorewall.sf.net. shorewall.net will continue to host the main FTP site along with the mailing list archives. http://www.shorewall.net will also continue to hosts the Shorewall 1.2 web site and will

-- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

I regret to announce that effective immediatly, CVS Web access will be by password only. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

This is becoming a FAQ and should probably be added to the docs. Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net ---------- Forwarded message ---------- Date: Sun, 28 Apr 2002 16:09:01 -0700 (Pacific Daylight Time) From: Tom Eastep <teastep@shorewall.net> To: Carl Spelkens

---------- Forwarded Message ---------- Subject: Re: [Shorewall-users] strange UDP scan results on a Shorewall=20 firewall Date: Sun, 3 Mar 2002 08:33:20 -0800 From: Tom Eastep <teastep@shorewall.net> To: "Scott Duncan" <sduncan@cytechconsult.com> On Saturday 02 March 2002 04:30 am, Scott Duncan wrote: > Yes, the net->all policy is the same on all three (REJECT log

On Fri, 26 Apr 2002, Ron Shannon wrote: > All points agreed. > > As you suggest, the docs are better if they''re a well-integrated set. If > a choice is made to exclude an advanced subject or level of detail from > the QSG, they should be covered elsewhere. As noted before, the docs as > a whole are exceptionally good. Your extra effort on the docs certainly > shows

Shorewall 1.3.9 is available. In this release: 1. DNS Names are now allowed in Shorewall config files (I still recommend against using them however). 2. The connection SOURCE may now be qualified by both interface and IP address in a Shorewall rule. 3. Shorewall startup is now disabled after initial installation until the file /etc/shorewall/startup_disabled is removed. 4. The

Tom, Thanks for all your hard work on this project. I will also volunteer to = help co-ordinate the Quick Start Guide, Samples and/or other = documentation efforts. If you have suggestions or "to-do" lists, they = would be helpful, of course. Steve H. (and interested others): we should probably keep further doc = support conversations off the announce list, probably just on the devel

Let me know if there are any problems. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

The ''firewall'' and ''functions'' file in CVS together produce a 30%+ speedup of ''shorewall restart'' on my firewall when compared to 1.3.11a. Please test with these files -- I don''t anticipate making any more performance changes for 1.3.12 and I want to be sure that I didn''t break anything. -Tom -- Tom Eastep \ Shorewall

Rafa³ Dutko has just discovered a potentially serious bug in version 1.3.0 and 1.3.1. In both versions, where an interface option appears on multiple interfaces, the option may only be applied to the first interface on which it appears. A corrected firewall script for 1.3.1 is available at: http://www.shorewall.net/pub/shorewall/errata/1.3.1/firewall and

In this release: 1. The ''try'' command now accepts an optional timeout. If the timeout is given in the command, the standard configuration will automatically be restarted after the new configuration has been running for that length of time. This prevents a remote admin from being locked out of the firewall in the case where the new configuration starts but prevents

Shorewall 1.2.4 will have the following changes: a) ''#'' comments now allowed at end-of-line in all config files. b) Firewall zone may be renamed c) Protection against concurrent state-changing operations (start, stop, restart, refresh, clear) d) ''shorewall start'' no longer fails if ''detect'' is specified for an interface with netmask

Apt-get sources are listed at: http://wecurity.dsi.unimi.it/~lorenzo/debian.html -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

Shorewall 1.3.4 is available: 1. A new /etc/shorewall/routestopped file has been added. This file is intended to eventually replace the routestopped option in the /etc/shorewall/interface and /etc/ shorewall/hosts files. This new file makes remote firewall administration easier by allowing any IP or subnet to be enabled while Shorewall is stopped. 2. An /etc/shorewall/stopped

The maintenance (adding RAM) took a little longer than I planned: 1) Shutdown - 1 minute 2) Open Case - 30 seconds At this point, I emember that I can''t add RAM to this box without removing the Mother Board (hinge-mounted in case) - slap forehead. 3) Remove cables, PCI NIC & MB - 2 minutes 4) Add RAM - 1 Minute 5) Get the %$#@ MB back in the case and aligned -- 15 Minutes 6)