Comments on: FMud update released

By: Jared

Jared — Sat, 14 Aug 2010 16:02:41 +0000

Hey I am trying to set up this fmud for my mud and I have the policy file being served from the same place as my game is running. Everytime I try to connect it keeps giving me a security error. My script is showing that it is connecting but its still not working correct. I have it using port 5000 for the policy file. The site demo is up at http://www.sinquestudio.com/mysticrune/fmud/fmud.html. Any help with this would be greatly appreciated.

Jared

By: Peter M Dodge

Peter M Dodge — Thu, 22 Jul 2010 00:58:06 +0000

It was, and is, but on another port now, as we figured it out on the NakedMud IRC:

Oh, duh! I know your problem.
A socket policy file served from a port >1024 can only authorize connections to ports >1024.
You need to serve the policy file from a port <1024 if you want to open port 23.

It works fine now that I changed the port! Maybe you could make a note of that, for future people like me wondering about that.

Thanks for the reply though :)

Cheers,
Peter M Dodge

By: matt

matt — Wed, 21 Jul 2010 09:56:12 +0000

Error: Failed to load policy file from xmlsocket://elvenblade.ca:27015

Looks like the policy file isn’t being served.

By: Peter M Dodge

Peter M Dodge — Tue, 20 Jul 2010 20:07:37 +0000

It seemed to have eaten the policy file in the comment display. If you need it please feel free to ask me and I can mail it, though I will note I -did- make sure http://www.elvenblade.ca where it’s being served from is in the file.

By: Peter M Dodge

Peter M Dodge — Tue, 20 Jul 2010 20:00:23 +0000

I am attempting to add a flash player to the mud that I have going as a pet project, using FMud, the policy file seems to get served up just fine, however I receive a ’security error’ with unspecific information.

This is the policy file:

I added several of the domain iterations to make sure that wasn’t the cause.

This is the actual page Im testing that doesn’t seem to work:

http://www.elvenblade.ca/FMud.html

The policy is served on port 27015 - the HLDS port - I used this one for testing purposes because I -know- it is unblocked (and unless I run my HLDS server, unbound, which - I made sure, Im not). You can TELNET to it and see - the connection does not get refused.

The actual game connects on the TELNET port - elvenblade.ca:23 that is.

Both myself and the other coder for my mud couldn’t seem to get this working, so I thought I’d ask here.

Cheers,
Peter M Dodge

By: Nil

Nil — Sat, 10 Jul 2010 22:12:05 +0000

Smashing. All up and running. I just installed the MUD engine in my server and imported the DB from the old one.

Better that way, now all is managed locally.

Thanks for the help, I’d have been running in circles forever otherwise.

By: matt

matt — Sat, 10 Jul 2010 18:20:10 +0000

The purpose of the policy file is to specify the domains which are allowed to make socket connections, so it makes sense that the policy file is on the same host as the one you are making the socket connection too. Otherwise anyone could host an app and give it permission to make socket connections somewhere else. Obviously this isn’t really relevant for MUDs as they are open to socket connections from anywhere anyway, but the system wasn’t designed by Adobe with MUDs in mind :)

Contact your MUD host and ask them to serve a policy file allowing connections from any domain on any port and that should cover anyone who hosts a MUD there.

By: Nil

Nil — Sat, 10 Jul 2010 17:17:58 +0000

Hm! Now I am a bit more lost, even.

So, should the same server where the MUD is (in this case delirium.isunlimited.net) have the policy and the python script serving it, with the HTML alone in the separate website where I am launching the client.

Think I’ll have to start hosting my own MUD, then. Can’t run python scripts from where my MUD is being hosted at the moment, nor open ports.

Thanks for the help though. Not really experienced with this stuff at all.

By: matt

matt — Sat, 10 Jul 2010 16:43:12 +0000

It should be trying to load the policy from bloodsunrising.com at 843

No it shouldn’t. The policy file has to be hosted at the domain you want to make a socket connection to, in this case delirium.isunlimited.net.

By: Nil

Nil — Sat, 10 Jul 2010 15:59:16 +0000

Thanks for looking at it, Matt.

843 on delirium.isunlimited.net is closed.

telnet delirium.isunlimited.net 2423 will give you the login for the MUD

telnet bloodsunrising.com 843 will just give you a blank screen as usual and I’ll get a notification in the nohup.out file accordingly.

The weird thing is that is is indeed trying to load the policy from delirium.isunlimited.net at 843. That of course should fail.

It should be trying to load the policy from bloodsunrising.com at 843 but connecting to delirium.isunlimited at 2423.