evangile wrote: so to eddy you know blizard agreement worth nothing? They have the right to block you if you violate the agreement. I know that they will from personal experience :laugh: The coding4fun article using C# wouldn't be a violation though, the interfaces are defined just as the plugin-system expects it. Injecting things in another way could be seen as an attempt to hack the system (e.g., someone who tries to change the amount of money that's stored in memory; such a thing is impossible to do, but they *can* detect attempts) Creating a mining-bot will get you in the same trouble, after some weeks. And why would you even want to, if there's a ready-to-run example in C# that you can customize to your own needs? They even explain how to make a Wow-like interface-window for your Tweets :) I are Troll :suss:

What if you connect a TCP socket to that IP and then check the RemoteEndPoint? It's a wild guess, but it could work.. or actually, it shouldn't. But if it does anyway, then it's cool.

Navajo Need custom software developed? I do C# development and consulting all over the United States. A man said to the universe: "Sir I exist!" "However," replied the universe, "The fact has not created in me A sense of obligation." --Stephen Crane

evangile wrote: net encryption is well know i'm pretty sure haker have already theyr tool for decrypt that in a click .Net contains support for a number of different encryption algorithms. All of which are publicly available, but this is not an issue. What makes the encryption secure is the Key(s) that are used along with the algorithm. Without those keys any hacker would have a hard time with decrypting the majority of the encryption algorithms in .Net - AES[^] would be a good option to go for... The main problem with encrypting data is where to store the encryption key(s) What users to you intend to have this client application that would want to hack it for IP information anyway? Is it a public client application connecting to a private server? In my opinion letting them no what your IP address and port number anyway is not an issue. If they are sending data over the net them im sure there are tool they can use to monitor data being sent to and from there computers which would reveal you IP address anyway. Plus any good hacker could scan you live server for any open ports surely? Just make sure you have a good firewall set-up Life goes very fast. Tomorrow, today is already yesterday.

There are few prof. that sells out idea how to implement using .net Are u ready to spend some $ for that?

A router that would allow TCP hole-punching would be "broken". UPnP is "difficult", there are far too many different implementations in routers, some of them really generous and allowing even the most the malformed request to open a port, others nitpicking about the number of spaces and refusing to even tell what went wrong. Ok so MSN does open a port? It still shouldn't need it but ok.. could you see whether it was UPnP-forwarded or opened as the result of outgoing packets? The router can not know that it was MSN though, so whatever it did, you can do the same. I recommend you use WireShark/Ethereal to capture how it opens the port (and look at Azureus as well, of course)