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 [ 01 | May | 2002 ]

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


Date: Wed, 1 May 2002 19:42:32 PST7
From: Sheridan George <s-geo@usa.net >
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.
=====================================================

Peter Skye wrote:
>

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

There is no place for the intruder to go in the hardware box, no handles to grab, and no well known OS
or application(s) with unlockable doors. I'm thinking more of a speciality box such as the SMC
instead of a separate PC running only a firewall such as InJoy.

I'm sure the SMC is breakable if an intruder can ascertain that it is an SMC, and the model (the BR
has a different controller than the ABR), the make of the imbedded controller, the OS, and the
language the program is written in. Once that stuff is known there are holes that can be found and
exploited.

Can you give
> an example of an intrusion methodology which succeeds for a common box
> firewall but fails for a separate box firewall?

No. I'm not into cracking computers. I got that info. (knowledge) from Gibson's site (
http://www.grc.com ) and from the talk he gave at NOCCC about two months ago. I do not understand all
I heard or read. Just that software firewalls on a production machine have to be engineered very
correctly to do the job without making matters worse. IIRC that goes for two NIC machines also.

Sheridan

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

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 [ 01 | May | 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.