There is a hole in your firewall 1

[iSeriesCodePoet]

In case you aren't aware, there is a hole in your fire. Here is the article that shows you where.

http://www.buzzsurf.com/surfatwork/

To summarize a user using SSH and Apache, could get through your firewall protections. VERY interesting read.

iSeriesCodePoet
IBM iSeries (AS/400) Programmer

Want to have all your bookmarks in one spot?

http://www.koldark.net/bookmark4u/

Make your links shorter:

http://makeashorterlink.com/

 

[Ntr0P]

Provided of course that you allow ssh out through your firewall in the first place.

 

[iSeriesCodePoet]

But this is using port 80. If you just block port 22, you won't stop them.

iSeriesCodePoet
IBM iSeries (AS/400) Programmer

Want to have all your bookmarks in one spot?

http://www.koldark.net/bookmark4u/

Make your links shorter:

http://makeashorterlink.com/

 

[JasonDeckard]

This isn't exactly ground breaking. You can get similar results by connecting to

https://www.megaproxy.com

The traffic between your browser and the proxy is encypted (as in the "shunnel&quot, and you are able to browse the web without concern for school/employer monitoring. The difference, from a network monitor's point of view, is that you are connecting to a remote host on port 443 instead of port 80.

 

[iSeriesCodePoet]

You can easily block websites, and ports. I actually posted it as a FYI for those that never thought of it.

iSeriesCodePoet
IBM iSeries (AS/400) Programmer

Want to have all your bookmarks in one spot?

http://www.koldark.net/bookmark4u/

Make your links shorter:

http://makeashorterlink.com/

 

[Sapient2003]

It isn't the firewalls fault anyhow. It is the service running on available ports that is the problem.

--Sapient2003 - sapient@sapient2003.com
"The worst insecurity is believing you are too secure."

 

[PcLinuxGuru]

It is actually very easy.

One: Block all traffic at firewall for your whole network

Two: Setup you own caching proxy server that changes the http headers going out (This is done so programs can't use your proxy for their connection)

Three: Setup Internal Caching DNS server

Four: Allow only the traffic from proxy IP and DNS IP

Five: Setup all IE with proxy info (can be done through Group Policies)

You just killed every software program out there including SSH, FTP, Kazaa, Yahoo, AOL, etc....