Re: Firewall workaround

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



most of the IM's today will try first it traditional ports, then 80,
then 443, then 23 , then 25.
Not using some tunneling of forwarding mechanism like ssh, just a single
connection trough this port.

I know ssh could forward ports, but in this case, you need the other end
where to forward the port :)



On Fri, 2004-01-16 at 13:54, Antony Stone wrote:
> On Friday 16 January 2004 4:38 pm, Alexis wrote:
> 
> > using port 80 may work too.
> 
> But SSH is designed to support port forwarding - it's part of the standard 
> operation.   On port 80 you'd have to come up with some mechanism of your own 
> and make it work.
> 
> Antony.
> 
> > On Fri, 2004-01-16 at 13:15, Antony Stone wrote:
> > > On Friday 16 January 2004 4:01 pm, Benjamin Dickgiesser wrote:
> > > > It would be realy nice if someone could help me with this:
> > > >
> > > > Situation:
> > > > I am useing a Windows XP PC at a student hall. To connect to the
> > > > internet I am useing the university connection. Unfortunatly there are
> > > > only around 5 open ports (80,21,22,23,6667).
> > > > My aim is to make a work around to this firewall.
> > >
> > > I'm not sure that's an appropriate quesion to ask on a security mailing
> > > list, but I guess you're right in assuming that this is a place to find
> > > people who know how to do it :)
> > >
> > > Anyway, my answer to your question is: why not just tunnel the protocols
> > > you want through SSH port forwarding?
> > >
> > > Antony
-- 
Alexis <alexis@xxxxxxxxxxxx>



[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux