Yes, FMS has extensive ways to protect the content. And it
has already been discussed in posts a while ago.
There is also a useful post on the blog of Kevin Towes,
Product Manager, FMS.
http://blogs.adobe.com/ktowes/
Correcting the reports, replay catcher has never downloaded
videos using RTMPE; it is just that it try to use RTMP url to
access the same stream and becomes successful if rtmp & rtmpe
both are enabled on target FMS (which is actually the default
setting on FMS3).
referring to Kevin's blog and other information around
adobe.com; I think that using any of the options below will block
replay catcher:
- using swf verification feature makes sure that only
specified custom swf(s) may connect to FMS.
- disabling RTMP is one way so that ONLY RTMPE connection is
accepted at FMS.
- The strongest of all is server-side action script; one can
write own connection authentication method in SSAS methods and RMI
client.onConnect() and client.call. this will make make sure any
client like replay catcher will just not able to comply with your
custom authentication routine as it would be unique.