Xavi,

You found really nice thing!

Would you like to share the code for using screen sharing which you used for
testing?

Best Regards,
 
Ashvin Savani - Arckid
Freelance Developer - Arckid.com
CTO - Avinashi.com
Team Macromedia Member - Flash
User's Group Manager - Gujarat

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Xavi Beumala
Sent: Tuesday, August 30, 2005 3:34 AM
To: Open Source Flash Mailing List
Subject: [osflash] About Breeze player

Hi all,
I'm guessing how illegal would be to launch breeze player with content 
that has nothing to be with breeze.

I think it's not a secret. With a simple for..in and ASSetPropFlags you 
can find System.Product and it's methods.

If you compile the following code you'll be prompted to install breeze 
addin plugin:

<code>
n = new System.Product("breezeaddin");
n.download();
n.launch();
</code>

I've done it and a new player (standalone) is installed in documents & 
settings folder. So that you can launch your own swf's in this new 
player as well as you can convert a loaded swf into an exe file.

The question is if this would break some eula...

This could be a way to break screenSharing. I've done some tests and I 
can get myScreen on a video movieClip without any problem. The problem 
is that when transmitting it throw FlashComm, FlashComm shuts down the 
connection (for sure it's a kind of server-side security). Maybe this 
could also be break with some kind of proxy wich would filter and 
analyze stream packets. Maybe flashcomm detects some bit in the packets 
to detect if it's a screenSharing stream or not (I'm not sure about this).

If we could detect this bit, change it in the proxy and then send to FCS 
the modified packet, would it be reverse engineering? would it break 
some eula?

Cheers
Xavi Beumala
http://www.code4net.com


_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org



_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to