SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 30 | April | 2002 ]

<< Previous Message << >> Next Message >>


Date: Tue, 30 Apr 2002 21:01:32 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: firewall failures

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

leganii@surfree.com wrote:
>
> I think you probably noticed that all the
> products mentioned in that article are
> peculiar to one particular venders OSs.
> http://www.newsbytes.com/news/02/176213.html

Peter Skye wrote:
> Who is the vendor? I've reread the
> article but don't see the common ground.

Sheridan George wrote:
>
> Sure you do - they are all software firewalls.

Umm, okay. "Windows"? I'm guessing.

Sheridan then added:
>
> Don't give me any sass about a hardware firewall being a
> software one in reality because software is what makes
> it go. A 'real' software firewall shares the CPU with
> the OS and other programs it is trying to protect. That
> is why they have a special vulnerability.

Okay. What difference does it make whether the firewall is
running on an independent box or on the application box? Can you give
an example of an intrusion methodology which succeeds for a common box
firewall but fails for a separate box firewall?

Or suppose you have a separate firewall PC with two NICs and
running a software firewall and all it does is forward packets (what
comes in on NIC #1 goes out on NIC #2, what comes in on NIC #2 goes out
on NIC #1) with appropriate firewall blocking of undesirable packets of
course. What's the difference if you then move the firewall software
from this separate firewall PC to the application (user's) PC? Why does
the system suddenly become more vulnerable?

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 30 | April | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.