Page 1 of 1

Web Client connection vs regular ones

Posted: 21 Apr 2015 12:08
by Aristos
This may be a dumb question, but I haven't been able to find the answer yet.

So, the address to connect to the game from a regular client is mud.genesismud.org port 3011 - now, this port is closed at work. Still, it is possible to connect via the web client. How? Does it use a different port?

Could one reproduce this on a regular client to be able to use a regular client? Meaning, connecting using a different address or port to be able to use a client like CMud or Mudlet from work.

Any hints are appreciated.

Re: Web Client connection vs regular ones

Posted: 21 Apr 2015 13:02
by Laurel
Aristos wrote:This may be a dumb question, but I haven't been able to find the answer yet.

So, the address to connect to the game from a regular client is mud.genesismud.org port 3011 - now, this port is closed at work. Still, it is possible toconnect via the web client.
There are various ways of managing your network in a company. Some admins allow gaming content, others dont. Some open port 3011, others don't. My company doesn't allow anything. I have access to this forum (for example) as an exception due to my job.

Re: Web Client connection vs regular ones

Posted: 21 Apr 2015 13:04
by cotillion
Web client traffic happens over https (port 443) and is encrypted and signed using TLS.
TLS is tricky to block without installing a new root certificate on all connected computers and then using a proxy.

You can most likely create an application which allows you to translate websocket to tcp which could be used to connect mudlet or cmud.

The websocket endpoint is wss://www.genesismud.org/websocket

Re: Web Client connection vs regular ones

Posted: 21 Apr 2015 13:07
by Alisa
Browser can have more ports open through firewall, than other programs.

Or browser uses port 80 to establish somehow.

Edit: cotillion for the win.

Re: Web Client connection vs regular ones

Posted: 21 Apr 2015 13:07
by Aristos
cotillion wrote:Web client traffic happens over https (port 443) and is encrypted and signed using TLS.
TLS is tricky to block without installing a new root certificate on all connected computers and then using a proxy.

You can most likely create an application which allows you to translate websocket to tcp which could be used to connect mudlet or cmud.

The websocket endpoint is wss://www.genesismud.org/websocket
Good one - thanks!

Re: Web Client connection vs regular ones

Posted: 21 Apr 2015 13:16
by Laurel
cotillion wrote:Web client traffic happens over https (port 443) and is encrypted and signed using TLS.
TLS is tricky to block without installing a new root certificate on all connected computers and then using a proxy.

You can most likely create an application which allows you to translate websocket to tcp which could be used to connect mudlet or cmud.

The websocket endpoint is wss://www.genesismud.org/websocket
It's easy enough to manage this via such things like Websense and block all "gaming" content (for example).

Re: Web Client connection vs regular ones

Posted: 21 Apr 2015 13:32
by cotillion
Laurel wrote: It's easy enough to manage this via such things like Websense and block all "gaming" content (for example).
Sure, Websense is a TLS MITM platform.
Once a company is willing to give all their private information to Raytheon and NSA all bets are off!