Loopback help

[zinverse]

Hi everyone,
This is my first post here...first thank you all for such a wonderful firewall:)
I am testing the new beta version of outpost i.e Outpost Firewall Pro ver. 2.5.365.4523 (366) and i liked the new features liek ad list import export too .
I connect to internet through local ISP and I have installed Miliki Dialup Accelerator to get image comptresion and virtual broadband. Hence whenever i am connected and i open things like Windown media player Yahoo messenger and Nero burning ROM etc. I get a message saying "Yahoo messenger wants to connect to localhost on port 8081" .....or a message like yupdater wants an outbound connection with local address 127.0.0.1 at port 8081 . What this results in is that I get messages like "You must update your yahoo messenger" etc...
If i don't use a proxy server(Like Miliki Dialup Accelerator) ...then It shows me Remote Host Address!! what i want to say is that I must always get to know where my computer wants to make a connection (Remote IP address or hostname) .... and i want outpost to show the Remote host instead proxy adddress!
Is there any way that I can do this???
I think current outpost system of showing "xyz application wants to connect localhost:8081" is VERY susceptible to Trojan connection Risks!!
Please telll me if there any way to show remote host while Using Proxy serevr or atleast for dialup webaccelerators!
Thank you :)

[David]

Hi zinverse,

You place me in the difficult position of asking where got that Beta Version of Outpost and where did you get the key. This particular part of our forum is only to support the latest public release. After I get those questions answered about the origins of your Beta Copy and the Key, perhaps we can move on. :)

[zinverse]

Hi David,
I use the sygate firewall after my outpost trial expired. and i told this to one of my college friends... he gave me the latest outpost beta version with 2 months beta tester's license or something. he is very intelligent in computers.
I am sorry but i can't install outpost 2.1 again as it said its trial expired so i only have this:( and seekinh help for this beta otherwise i will have to move to sygate because I don't think outpost is safer as long as it has this loopback flaw.
Thanks for ur fast reply David. are you the Administrator of Beta testers? Thanks

[David]

Hi zinverse,

Ok......well that beta a few versions older anyway. I understand your position. I do not believe that Outpost will see the remote address in this case because everything is directed toward the proxy application running on your PC. However, Outpost should see the remote addresses accessed by the proxy application. So, the information should be available to you. Other than those comments, I can only offer you a few reading suggestions that may help answer your questions about securing against trojans when local proxies are used. Read these:

1. 1

2. We have had a lot of discussions here regarding the security of local proxies like yours. Most of those discussions have focused on Proxomitron, but the principle is still the same. You might try using our forum search function to find more information.

3. See the Outpost V2 FAQ. There is a lot of good information there.

And to answer your last question, Agnitum Administers the beta software and mailing list. We administer beta discussions for the Beta Forum. By the way, anyone can apply to be a Beta Tester throught the Agnitum site, including you.

I just wanted to try and be a little helpful. No more support will be given on this issue due to the nature and source of the Outpost software that you are using. Oh and by the way, it is Sygate that has had a long standing and known problem handling Loopback connections. Outpost has always been way ahead of Sygate in this respect as well as many others.

THIS THREAD IS CLOSED.

Have a nice day. :)