similar to: CVS Web Access Is Now by Password Only

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

On Wed, 5 Jun 2002, Ron Shannon wrote: > Bummer. Will the robots.txt handle it? (http://httpd.apache.org/docs/misc/howto.html#stoprob) > Nope -- most of the offending bots just ignore robots.txt. The CVS interface is still available at: http://www.shorewall.net/cgi-bin/cvsweb.cgi There is just no link to it from the index. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM:

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 \

-- 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

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

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

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

There is now anonymous readonly CVS access available from :pserver:anonymous@cvs.shorewall.net:/usr/local/cvs (no password required). Projects are: Shorewall = Shorewall less documentation Samples = The sample configurations Shorewall-docs = The Web site/Documentation -Tom Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \

There is also a project called ''Samples'' that contains the sample files. -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

The ''firewall'' script currently in the /Shorewall CVS project: a) Is approximately 15% faster starting/restarting on my configuration -- please report your experiences with it. b) Reloads Traffic Control/Shaping as part of "shorewall refresh" c) Turns off the shell trace after an error has occured (except when the command being traced is "stop" or

I''ve corrected my HTDIG configuration so that it doesn''t fall into the symlink loop created by the 1.3 beta documentation. Sorry for any inconvenience, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

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

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

This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. ---1463811327-1716203191-1023027413=:9844 Content-Type: TEXT/PLAIN; charset=US-ASCII ... that doesn''t have a broken "show log" command :-/ -Tom -- Tom Eastep \

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

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

I have purchased a license for Vexira MailArmor (an antivirus product) and the good news is that it is installed and working at shorewall.net. The bad news is that I have yet to get Vexira running together with SpamAssassin :-( As things currently stand, list posts will be protected from viruses but may contain Spam. I''ll continue to work to correct this situation. -Tom -- Tom Eastep

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