#1 Proxy only certain user-configured ports
I love transconnect but I only need it for one thing:
NNTP (news) access. I am behind a firewall which blocks
all but HTTP access. I can use regular HTTP proxy
settings in various apps directly, which seems to work
best for me. Some protocols I prefer to proxy using
SOCKS5. Also the local-network configuration is too
complicated to set up explicitly. So really the only
thing I wanted transconnect to do was proxy NNTP, which
Mozilla will not do for you.
So this patch lets you specify that only certain ports
be proxied. You can just add the ports (numbers, or
service names) to the config file with the "service"
directive.
The patch includes the code change as well as changes
to the INSTALL doc file and the sample config file.
I have tried the patched transconnect and it seems to
work for me. The patch is not very complicated anyway.
Suggested patch
Logged In: YES
user_id=257383
BTW you should also do this:
echo tconn.so > .cvsignore
cvs add .cvsignore
cvs ci .cvsignore
to make sure that you do not see "? tconn.so" when updating
sources after running a build.
Logged In: YES
user_id=257383
Minor bug in patch:
fprintf (stderr, "Unrecognized service port or name: %s", cp);
should of course read:
fprintf (stderr, "Unrecognized service port or name: %s\n", cp);
Logged In: YES
user_id=257383
Let me know if you would like a patch against TC 1.3 Beta
sources. The patch given here is against CVS trunk sources
which are apparently obsolete.