On 19 May 2006, at 10:56, Dave Cridland wrote:
On Fri May 19 10:50:29 2006, Karim Bernardet wrote:
I have coded a client and a server which use a simple TCP
protocol to communicate. Each one is behind a firewall and to
bypass the firewall (outgoing connections permitted), I use ssh
tunneling between them. But now I have to install the client on a
computer which is behind a firewall too (outgoing connections
permitted), so problem ...
No problem at all. You reconfigure the firewall to allow your
protocol through. Simple, isn't it?
If you can't, or your administrator won't, then your protocol
should not be going through the firewall.
"Bypassing firewalls" is traditionally called "cracking". It's only
comparitively recently that people have felt the bizarre need to
wrap every protocol in HTTP in the belief that if they don't have
to reconfigure a firewall, this makes things more secure.
But he /is/ allowed outgoing connections, so changing to a non-p2p
protocol is hardly hacking.
To the OP:
Jabber is (mostly, with a small exception) server-based, so if you
can run your server somewhere with incoming connections permitted,
you can connect from anywhere which permits outgoing connections with
no form of tunneling (although there are methods for tunneling
through limited outgoing connectivity). Iris is indeed a decent C++
library for Jabber.
/K
--
Kevin Smith
Psi Jabber client developer/project leader (http://psi-im.org/)
Postgraduate Research Student, Computer Science, University Of Exeter
