| From: | Todd Montgomery <tmont@****.WVU.EDU> |
|---|---|
| Subject: | Firewall |
| Date: | Mon, 12 Jul 1993 11:15:07 -0400 |
I have worked as a SysOp for a Unix based BBS for two years, The
system went off-line on May 16th. And now I am working in software
engineering research. Before that I ran my own PC-based BBS for
almost 6 yrs.
I am familiar with the concept of Firewalls. ANd I have discussed how
they can be defeated with several people. The answer is, as far as we
could figure without actually trying it, using the basic operation of
switching between system and system to your advantage. Basically, why
do you need to have a two way connection? Chances are you know what
you are after anyway. So just make a script, embed it into the file
area to be transferred, and include a self-extracting process
dispatcher to take over the processor when it is activated by A) file
operation, or B) file execution. Basically it is a Jerusalem type
virus but instead it overrides the processor and copies sensitive
files to non-sensitive file areas that need to connect to the outside
world (which is how they are supposedly set up). Then it goes dorment
and erases itself from the embeding file. The only immediate problem
is that a virus scan may detect it. But that is something which can
be fixed with a minimum of ease. ( I refuse to elaborate on this).
When the files storing the info access the outside world, bingo. This
is just one possible scenario I have worked out with some other SysOps
that have actually dealt with Firewalls. But this theory has not been
tried. Also according to them, it is a hardware latch that prevents
the switching from being two-way. The hardware is not designed to be
two-way.
-- Quiktek
a.k.a. Todd Montgomery
tmont@****.wvu.edu
tmont@***.wvu.edu
un032507@*******.wvnet.edu
