||unity-dev|| FYI: Flash Player 9, 0, 115, 0 security hardening can break U2 and other socket server sites!

I just took a look at the new security stuff and it looks to me like you just need to serve a policy file from your socket server over port 843.  All the policy file does is say what domains/IPs are allowed to access your socket server and what ports your socket servers allow.  You don't need to force people to connect to port 843. Doesn't Unity allow you to specify the policy port? 


DC


----- Original Message ----
From: Discussion list for Unity developers. <unity-dev at moock.org>
To: unity-dev at moock.org
Sent: Friday, December 21, 2007 8:42:07 AM
Subject: Re: ||unity-dev|| FYI: Flash Player 9, 0, 115, 0 security hardening can break U2 and other socket server sites!


Thanks for the info Jayson.  I hadn't looked at the new release notes
 on the
new Flash player so this was interesting news to say the least.  It
 looks
like in reality a person might as well run their socket server on port
 843
from now on and serve the policy file through it, then allow the
 connection
on that same port or else you have to run two instances of a socket
 server
or one that can use multiple ports.  The document seems to indicate
 that in
phase two if a firewall is blocking you well then your out of luck.
Probably makes sense to have a "Policy Server" now and then the actual
"Socket Server".


Chad


On Dec 20, 2007 11:21 AM, Discussion list for Unity developers. <
unity-dev at moock.org> wrote:

> www.adobe.com/devnet/flashplayer/articles/fplayer9_security_04.html
 (the
> whole article is a must-read, but, this is the critical page)
>
> Flash Player 9,0,115,0 introduces new security measures that cause a
 flash
> SWF running in it to "make contact" via PORT 843 during xmlsocket
> connections!
--
you're a unity-dev subscriber. to unsubscribe, visit
 www.moock.org/mailman/listinfo/unity-dev/

superb hosting for this list and moock.org is generously provided by
 Rackspace. See: http://www.rackspace.com/?supbid=moock