The use case I've heard that makes sense to me that does provide security is this.
Say you have a bunch of FLVs stored on your server and you let some people access those from their site. And at some point you discover that someone has been abusing that privilege and racking up huge bandwidth charges for you. So you add the cross domain and deny access to certain sites. Then you can still stream them out, but the "friend" that posted it to slashdot is no longer able to. Make sense? It's not a lot of security in my opinion, but it works. There are ways around it, like proxies, but then those people will be using the bandwidth themselves as well. On Oct 26, 2007, at 8:26 AM, geoffreymina wrote: > Say there is a site which has a crossdomain.xml defined: > > http://www.foo.com/crossdomain.xml > > with > > <allow-access-from domain="*.foo.com"/> > > If I were to load an SWF file on my internal webserver and create a > local host file which contained an entry for fake.foo.com could I then > load the SWF file from fake.foo.com and access data on www.foo.com? > > If this is the case, then it seems to me that crossdomain.xml is > really > just something to make people feel warm and fuzzy... and not at all a > real security measure. > > Thanks, > Geoff > > > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders% > 40yahoogroups.com > Yahoo! Groups Links > > >
