Friday, August 8, 2003, 7:33:49 AM, I wrote: D> Here's how it would work: D> 1. I have a program listening on localhost:25 (local SMTP) D> 2. A connection to that port causes the launch of the external D> program with that connection passed to it as stdin. D> D> Hmmm. As I wrote this, I realized this is the standard inetd D> program in Unix. No need for TB! to try multiple times. I'll D> have to see if Cygwin already has an inetd and give this a D> try!
Well, it didn't work. TB! connects to the port inetd is listening on fine and the ssh program looks to get launched. The problem appears to be that when inetd attaches the TB! connection to ssh it connects to ssh's stdin rather than the tunnel port. This is correct behavior on inetd's part. So, it might be time for custom code or, more likely, live with my current solution. Thanks for y'all's input! -- Dave Kennedy ________________________________________________ Current version is 1.62r | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
