So basically even if you have the correct URL, that URL won't "work" unless you are a logged in, authenticated user. Our proxy is in the same VPC and deals with the inbound request (checking the security header). We request the actual (unencrypted) content on S3, residing in a private bucket. Hey - Actually we always override the native player tech (no matter what the browser) so we can set a security header on the request. Maybe we are missing a step that can prevent this any info would be appreciated? We recently viewed a post here: videojs/videojs-contrib-hls#1337 about possibly obfuscating the requests. Simply install the extension in Firefox and then install the companion app and click download and covertĬan anyone suggest any way to prevent this I totally understand that its pretty much impossible to prevent videos from being stolen simply using screengrab software will do the job and nothing can prevent this but it would be good to prevent simple downloads from extensions make it as hard as possible? We have spent quite a bit of time trying to provide the best possible security by encoding our media through AWS with AES 128 bit encryption this has worked great for a long time but like everything on the web we have been shown that this can be easily downloaded using the following plugin.
0 kommentar(er)
