TWGS sending server information to EIS

Microsoft has nothing on JP. Any TWGS version above 2.07 sends your private server information to EIS. Just thought everyone should know this.

Big D wrote:Microsoft has nothing on JP. Any TWGS version above 2.07 sends your private server information to EIS. Just thought everyone should know this.

What information is being sent?
Has anyone used wireshark to investigate the packets?

Oso wrote:

Big D wrote:Microsoft has nothing on JP. Any TWGS version above 2.07 sends your private server information to EIS. Just thought everyone should know this.

What information is being sent?
Has anyone used wireshark to investigate the packets?

We were told that it sends login and server activity, but I'm also assuming it checks for valid registration, server up time/down time, and possibly more. I haven't investigated to find out exactly what information TWGS sends to EIS. The only way to really stop this would be to block the program with your firewall, but then if you do, it will also block any incoming activity. Pretty much defeats the purpose of a public server then.

I also found out that TWGS (any version higher than 2.07) sends each players IP address to EIS when they log into that server. Even if you turn off jumpgate, it's still going to send that data to EIS. It's not optional.

Big D wrote:I also found out that TWGS (any version higher than 2.07) sends each players IP address to EIS when they log into that server. Even if you turn off jumpgate, it's still going to send that data to EIS. It's not optional.

I know a way of blocking it which does not require a firewall.

Oso wrote:

Big D wrote:I also found out that TWGS (any version higher than 2.07) sends each players IP address to EIS when they log into that server. Even if you turn off jumpgate, it's still going to send that data to EIS. It's not optional.

I know a way of blocking it which does not require a firewall.

Please let us know how, not that I'm going to run v2.xx anytime soon, but there are probably plenty of sysops that would like to know this information.

Big D wrote:

Oso wrote:

Big D wrote:I also found out that TWGS (any version higher than 2.07) sends each players IP address to EIS when they log into that server. Even if you turn off jumpgate, it's still going to send that data to EIS. It's not optional.

I know a way of blocking it which does not require a firewall.

Please let us know how, not that I'm going to run v2.xx anytime soon, but there are probably plenty of sysops that would like to know this information.

This is for informational use only- if you screw your own system up with this then it sucks to be you and it isn't my fault.

On every Windows system there is a HOSTS file. It is usually found in the c:windows\system32\drivers\etc folder.

Open it with notepad and add an entry that says:
127.0.0.1 <EIS Server addy>

Then save the file and you're good to go. Every time it tries to send, it will fail as it is sending to your local pc. Granted, it might also mess up your access to the forums and such, depending on how JP has his system set up. I don't know what the EIS server address the data is going to, so there you go.

I'll be willing to answer more questions later, but my time is up and I'm heading to my internetless home. *sob*

Wouldn't this be useful to actually track how many people are still playing the game? Just because there's a IP addy out there and it's being tracked how would he be able to exploit it? This would be a useful tool in future expansions of the game (more than just text based of course) when I played other online games you have to register with a email addy and what not. It also logs your IP address. If I'm way off from the picture please enlighten me.

Comet wrote:Wouldn't this be useful to actually track how many people are still playing the game? Just because there's a IP addy out there and it's being tracked how would he be able to exploit it? This would be a useful tool in future expansions of the game (more than just text based of course) when I played other online games you have to register with a email addy and what not. It also logs your IP address. If I'm way off from the picture please enlighten me.

Well this wouldn't be an accurate way to track how many players are playing the game simply because all players don't have static IP's. Many players still have dynamic IP addresses. As far as the sending any information to EIS, many sysops will have a problem with this. Also I'm not even sure it is legal. It's one thing for a website or server to obtain information, but when this website/server passes that information out to other parties, then it becomes a security issue. Player > TWGS Server > EIS > who knows. I personally as a player don't want my IP address passed on any further than the TWGS server that I'm playing on.

Big D wrote: I personally as a player don't want my IP address passed on any further than the TWGS server that I'm playing on.

After all its not like your ip address is shared with every packet you send on the internet.

R

ReaperTW wrote:

Big D wrote: I personally as a player don't want my IP address passed on any further than the TWGS server that I'm playing on.

After all its not like your ip address is shared with every packet you send on the internet.

R

Actually no it's not. I run a proxy most of the time I'm surfing.

BTW, your signature script says:

Your IP is 208.115.207.43! Your ISP is Patriot Media and Communications

Not even close. ROFL

Big D wrote:Not even close. ROFL

Yea, but is he ever?

Big D wrote:
As far as the sending any information to EIS, many sysops will have a problem with this. Also I'm not even sure it is legal. It's one thing for a website or server to obtain information, but when this website/server passes that information out to other parties, then it becomes a security issue. Player > TWGS Server > EIS > who knows. I personally as a player don't want my IP address passed on any further than the TWGS server that I'm playing on.

Actually, it is legal. We develop software (games and applications ourselves). Since the TWGS software is still in a "Beta" stage, he can collect connection information to help track what he needs. He is not allowed to take that information and sell, give, pass on to any third party without the consent of the person(s) involved. In other words, he would need the permission from each individual to do so. I do agree that it is not exactly a good thing when a sysop here's things like that, but as a developer myself I know the reason why. And people should always remember in any "BETA" that could happen and should be aware of this. We have our own written software to block things like that, so it does not affect us. But Oso is correct on a quick solution.

Comet wrote:Wouldn't this be useful to actually track how many people are still playing the game? Just because there's a IP addy out there and it's being tracked how would he be able to exploit it? This would be a useful tool in future expansions of the game (more than just text based of course) when I played other online games you have to register with a email addy and what not. It also logs your IP address. If I'm way off from the picture please enlighten me.

As a general rule I do not like things that "phone home". Privacy is extremely valuable, especially in an online environment. Yes, it would be nice to know actual numbers, but at what cost? If you follow this to its logical conclusion, then this information could be used for more than just reporting. Remember when they put in the seatbelt law saying they'd never pull you over for it?

ReaperTW wrote:

Big D wrote: I personally as a player don't want my IP address passed on any further than the TWGS server that I'm playing on.

After all its not like your ip address is shared with every packet you send on the internet.

R

Technically, it is.
Each packet you send has your IP address, the recipient's IP address, and the data you are sending.

Routers use the headers in your packet in order to know where to send your packets. Anywhere along the line your packets can be "sniffed" and their contents displayed to whoever is using the sniffer. Notable exceptions are for SSH and SSL connections.

One thing that would be nice is if TW2002 could run on an SSH connection instead of a telnet one.