31 ms·
There'a been explpots in image, video, and audio codecs... Which is why it's important to protect your users, but also your servers... Best to sandbox/jail/etc
by toast0 3y ago
There'a been explpots in image, video, and audio codecs... Which is why it's important to protect your users, but also your servers...
Best to sandbox/jail/etc as tightly as possible, and limit the codecs to only what you need. You can configure the ffmpeg builds pretty granularly... default will include too much.
- beeboobaa3 3y agoI care more about protecting my servers than my users. If one user attacks another that's not really my problem, blame can easily be shifted to the browser. But if someone hacks my servers and leaks everyone's data, that's my problem. So not encoding is probably the safer way to go for the business.
- mthoms 3y agoYikes. What if the other user getting attacked is you or another admin on your team? Now the attacker has admin access and can compromise your servers and “leak everyone’s data” just fine. I don’t think you’ve thought this through.
- bawolff 3y agoTrust me, your website will always get blamed regardless of its a user fault. If websites get blamed when users reuse passwords, they are definitely getting blamed if you distribute malicious files.
- theendisney 3y agoYou can think that but you should never say or write it. :p
- beeboobaa3 3y agoIt was just a joke, your honor.
- theendisney 3y agoI got the picture.