Skip to main content
A
Anonymous
January 11, 2017
Question

v24.0.0.194 breaks flash embed chats.

  • January 11, 2017
  • 3 replies
  • 41697 views

Just looking to see what has changed from 186 to 194 that stops flash based chats from connecting. When using 186 connection was fine. As soon as updated to 194 same chat gets a flash policy error even though flash policy is running. only thing to change was updating to the new flash player version. This is effecting both microsoft edge/ie and firefox. Not effecting google chrome as of yet as they haven't updated to the new version.

    This topic has been closed for replies.

    3 replies

    A
    Anonymous
    January 14, 2017

    Hello,

    I am still in doubt.that It should be better to use "to-ports="6667" value"

    But when I do enter a port then I get the flash policy error again. So for now I use  to-ports="*" (with a star)

    Is there someone who can tell me  what to do so I can use "to-ports="6667" value" ?

    Best regards, Herman.

    jeromiec83223024
    Community Manager
    jeromiec83223024Community Manager
    Community Manager
    January 14, 2017

    The socket policy file tells Flash Player what ports it's allowed to communicate on.  The value foo in to-ports="foo" is the list of ports you want to allow.  If you've modified your instance to use 6670 instead of 6667 as an example, then you would want to specify:

    <allow-access-from domain="mysite.com" to-ports="6670"/>

    You can also specify a comma-separated list, or a range, like:

    <allow-access-from domain="mysite.com" to-ports="6670,6671,6673"/>

    <allow-access-from domain="mysite.com" to-ports="6670-6679"/>

    A
    Anonymous
    January 14, 2017

    yes but the problem is untill now, when I specified a port in flashpolicy.xml Again I get flashpolicy error.

    Thats whyI ask the question,

    For now I use * (star) instead of a portnumber. But it is not safe or not safe enough.

    Best regards, Herman

    A
    Anonymous
    January 11, 2017

    Unfortunatly we also have this problem with Adobe Flash Player. People can not connect to our LightIRC webchat application.

    They get error about flash policy daemon should not be installed. But it is installed and running. We have these problems since yesterday update from Adobe Flash Player.

    Best Regards, Herman.

    jeromiec83223024
    Community Manager
    jeromiec83223024Community Manager
    Community Manager
    January 12, 2017

    Sorry for the inconvenience.  Flash Player has historically blocked communication on a number of ports.  As Flash and the Internet continue to grow and mature, it's important that Flash behaves as a responsible citizen in regard to the larger ecosystem.  In many instances, this means ensuring that Flash Player conforms to limit its capabilities to match those available through HTML and JavaScript.  These changes bring Flash Player in line with the latest thinking about what ports should be restricted.

    While updates to the official documentation are forthcoming, I can confirm that we've expanded the list of blocked ports.  Here's the current list:

    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.

    Unfortunately, one of the side effects of this change is that a few of these ports are in the range of ports informally used by IRC servers when an IRC daemon is not run with administrative privileges, or many IRC instances are served from a single IP.  In this instance, our recommendation would be to proxy traffic on affected ports in this range to different ports, in order to make them available to a Flash-based IRC client.

    The message about installing a policy daemon is generated by the content, and is incorrect.  In this instance, you're encountering the error because you're attempting to connect to a port that's blocked, and it fails.

      A
      Anonymous
      January 12, 2017

      Hello Jeromiek,

      With the help of your answer we could fix this isue. Thank you verry much. What did we do?

      <?xml version="1.0"?>

      <!DOCTYPE cross-domain-policy SYSTEM "/xml/dtds/cross-domain-policy.dtd">

      <cross-domain-policy>

      <site-control permitted-cross-domain-policies="master-only"/>

      <allow-access-from domain="*" to-ports="6667" />

      In the last line remove 6667 and replace that with a star *

      Then think about what port you would like to use and put that port in a listen block in your Unrealircd.conf  and in Lightirc in config.js put that same IP      in params.port                         = "ooooo"; replace the zeros. When you finished then /rehash you unreal server. and also after the changes you made in restart the flashpollicy. Good luck and get it up and running again>

      Best Regards, Herman.

      divya010193
      Adobe Employee
      divya010193
      Adobe Employee
      January 11, 2017

      Hi,

      Which operating system are you using.?

      Also, Please share a snapshot of the "error" as you mentioned above.

      Thanks!

      A
      Anonymous
      January 11, 2017

      Im currently on Windows 10, but it happens on any OS i believe as we have had reports of issues on mac aswell. This happens on any type of web based flash chat. lightIRC is one of the ones I use that is having the issue: you can test with:
      ChainScriptz

      also happens on oasiz chat ( Oasiz Home  )

      and buzzen chat ( Buzzen Chat - Free Chat Network )

      All three of these use different flash compenents to their chat so it is a wide spread issue with connect to chat networks using flash.  All of them use so variation of an irc chat backend ( hence the flashpolicy being need ) 

      divya010193
      Adobe Employee
      divya010193
      Adobe Employee
      January 11, 2017

      Thanks for reporting. We are investigating the issue.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices