OT-Re: Question on email virus in Outlook Express

[Brian Densmore]

Sigh. This would be hilarious if it wasn't so damn sad.

When are those M$ people going to get a clue? Well good news around the
bend. With the stable release of Wine 1.0, maybe it won't be an issue
anymore. I am going to bring home a proprietary app I use at work and
see if I can get it to install and run under Wine. The need for this one
app is the only reason I have a M$ partition on my notebook. It sure
would be nice to free up all that diskspace. :')
And if it becomes necessary, I may also get my company to get me a copy
of Crossover for Office. Sadly though, this will be a game of always
being one step behind M$. When Office XP2003 comes out we'll see all new
proprietary formats.

<rant>
And since we're off-topic, a rant.
Got Linux Firewalls, Second Edition (Zieglar/New Riders) over the
weekend.
Excellent book, but ... written in M$ Word!!!!!!!!!
I'm -=really Pissed=-! 
I didn't look at the back inside cover before buying ( I was too busy
enjoying the content).

Review: Once you get past the editing software issue, the book is well
organized. A brief lesson on the internet protocols and fundamentals,
security issues and what a firewall is. Then straight into a description
of iptables, with some reference to ipchains. The remainder of the book
builds a iptables firewall step by step explaining what, how, where, and
why (chapter 4). Then optimizing the firewall (chapter 5), and then on
to advanced issues (6 & 7), debugging (8), and security & monitoring (9
thru 13). The appendices give the firewalls built in the chapters in a
complete view and support scripts.
An excellent tutorial, and reference with plenty of internet references.

Any user could easily build a nice firewall with the instructions
provided within.

I would rate this with 5 penguins if not for the M$ issue.
rating: 4 penguins
</rant>

Brian

[snip]
> 
> You're correct.  This has been discussed a bit lately on 
> BUGTRAQ.  A good
> description of the problem can be found at
> http://online.securityfocus.com/archive/1/263469.
> 
[snip]