Great Circle Associates Firewalls
(September 1996)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Blocking non-http (executable) content
From: peter @ baileynm . com (Peter da Silva)
Date: Fri, 30 Aug 1996 09:25:42 -0500 (CDT)
To: Russ . Cooper @ RC . Toronto . on . ca (Russ)
Cc: Firewalls @ GreatCircle . COM, DCOM @ Listserv . msn . com
In-reply-to: <c=US%a=_%p=Toronto%l=MAIL-960830132632Z-20 @ mail . rc . toronto . on . ca> from "Russ" at Aug 30, 96 09:26:32 am

> If, for example, every standard HTTP proxy recognized images, which
> typically have some sort of header text, and ASCII text, then the proxy
> could prevent any code blocks that contain anything else. This would
> eliminate the need to constantly modify the proxy for new innovations.

Tunnel 1:
  begin 664 packet
  MKJhJKHsjkHJKAShjkHJKDFHKJDWHFJKWHDJKFHJKFDLWJDHJKWHJKCHJK
  MjhewfgdkjfhjkhKJHWJQKhJKH JKhJK HWQJKHKJhDJKH DJKWHJKDjhj
  'kljdshsjk
  end

Tunnel 2:
  lorum ipsem dolor sic amet. gang five sleep dupe new diet green
  lemming infinity truth sex gnoll trust 1984 meddle plug sing.

Basically, if we can't come up with a platform to let them easily punch
through firewalls with our approval, they'll do it without. SOCKS used
to be thought of as a security problem. By comparison with this it might
be our last best hope.


Indexed By Date Previous: Re: Dcom Rollout (fwd)
From: peter @ baileynm . com (Peter da Silva)
Next: Re: Blocking non-http (executable) content
From: peter @ baileynm . com (Peter da Silva)
Indexed By Thread Previous: RE: Blocking non-http (executable) content
From: Ian Miller <firewalls @ scientia . com>
Next: Re: Blocking non-http (executable) content
From: peter @ baileynm . com (Peter da Silva)

Google
 
Search Internet Search www.greatcircle.com