cocoaforge

I only noticed this through pure luck, when trying to get a local network user to browse to my PC;

Adium .80 seems to kindly convert my local IP address (192.168.0.15) to my routers real world ip address (82.217.x.x).

How is it possible to stop it doing this.

1) I see it as a security issue (as it doesn't tell me its changed it)
2) It makes sending local links impossible.
3) It... well, it scares me, OK?

WIth thanks,

MidnighToker

Interesting. What protocol are you using? I don't know of anything in Adium that does this; it sounds like a protocol-specific thing. MSN is particularly prone to doing stupid things like this.

well this was over MSN.
Hold on, i'll do some investigating.

well i'll be...

It is MSN.

Type in 192.168.0.10 (laptops IP Address, Windows XP running Trillian) and it kindly replaces it with my external IP.

The shocking thing, is that it half makes sense, and would stop conversations like the follwing
"OK Stephen, so whats your IP that you want me to VNC to, then?"
"Its 192.168.0.5..."
"For G-d's sake man, you're half way through your CCNP....."

but its still.... worrying.

Dont suppose anyone's got any thoughts on this?

That's very worrying. Use AIM!

ok, so the interesting thing was this.

in tests conducted earlier with a friend of mine (on a seperate network, both using Adinum both MSN) we had all of our messages encrypted.

So, the question i have to ask, is how did it replace them.

If encryption happens in Adinum, then the message should be sent through MSN as encrypted data, so the MSN protocall cant read the message and make the IP Swap.

Any thoughts?

I am unable to reproduce this with MSN & Adium.

MidnighToker wrote:ok, so the interesting thing was this.

in tests conducted earlier with a friend of mine (on a seperate network, both using Adinum both MSN) we had all of our messages encrypted.

So, the question i have to ask, is how did it replace them.

If encryption happens in Adinum, then the message should be sent through MSN as encrypted data, so the MSN protocall cant read the message and make the IP Swap.

Any thoughts?

Then it's not MSN doing it—it's the local client doing it before you send the message, going out like "whatismyip.com" does and finding your external address, piping it back in and sending it off in your encrypted message.

Not that I'd really have any clue—I hate MSN and have no reason to use it, so I don't. I'm just guessing, and that seems the most likely.