The upgrade to v18.104.22.168 has broken our flash based chat client. When trying to download the flash policy from our flash policy server the following is occuring:
SecurityError: Error #2003: Invalid socket port number specified.
Setting EnableInsecureSocketPorts=1 in the mms.cfg file resolves this issue, however we cant get our customers to make this change.
Our action script currently loading the policy though an xmlsocket:// call.
What do we need to do to resolve this and get our chat working again without the work around?
Thanks for reporting. We are investigating the issue.
While updates to the official documentation are forthcoming, I can confirm that we've expanded the list of blocked ports to include the following:
1, 7, 9, 11, 13, 15, 17, 19, 21, 22, 23, 25, 37, 42, 43, 53, 77, 79, 87, 95, 101, 102, 103, 104, 109, 110, 111, 113, 115, 117, 119, 123, 135, 139, 143, 179, 389, 465, 512, 513, 514, 515, 526, 530, 531, 532, 540, 556, 563, 587, 601, 636, 993, 995, 1720, 1723, 2049, 3659, 4045, 5060, 6000, 6566, 6665, 6666, 6667, 6668, and 6669.
To resolve this issue, our recommendation would be to modify your content and corresponding socket server to use a port that's not included in the list above.
going through the blocked ports I found port 531 which is the port that the scratch team uses for their cloud data server. because this port has been blocked scratch members are having repeated problems using the (extremely slow) https fallback polling method instead of the fast 531 port to play and make their projects. I doubt the port they use will be changed as it would take too long with them making the new 3.0 update (completely remade in html5). if port 531 could be unblocked it would help out thousands of other people and would be greatly appreciated.