I've looked through the man pages, FAQ's, examples, and found one post (without a reply: http://stunnel.mirt.net/pipermail/stunnel-users/2005-May/000487.html) about this, but still don't have my question answered.
I have a machine outside the firewall (let's call it outThere) that needs to connect back to a machine inside the firewall (let's call in inHere) for backup procedures. Now, because of the firewall, outThere cannot connect to inHere, but inHere can connect to anything on outThere that it wants.
Can I initiate an stunnel connection from inHere to outThere, and then have stunnel on outThere listen on a localhost port, which, when connected to, would actually forward the connection (over SSL) back to a configured port on inHere? Is this at all doable?
j----- k-----
Joshua Kugler wrote:
Can I initiate an stunnel connection from inHere to outThere, and then have
stunnel on outThere listen on a localhost port, which, when connected to, would actually forward the connection (over SSL) back to a configured port on inHere? Is this at all doable?
That is more of a question about your firewall than stunnel. What you might be looking for is "port triggering" and if it's not your own firewall where you'll have admin access to change this, you don't have much hope. There ARE ways around it but, again, they have nothing to do with stunnel. Tunnelling is what you want, you just need some support software to accomplish it.
-
Eric Haddix -
Joshua Kugler