For #DevOps teams not yet using Blitline's file processing API in your platform infrastructure, don't forget to update your #imageprocessing libraries. #OpenJPEG CVEs found https://t.co/4tBll9buXc.
@DAMNEWS Thanks for your guest post on @blitline's IPaaS Blog. We're definitely encountering the 'to insource' or 'not to insource' #imageprocessing question more frequently with DAM & other #software customers as they work to lower technical debt & free time to focus on core product.
Blitline has partnered with AWS and offers EventBridge integration instead of using Blitline postback calls. More secure and inside your VPC you can manage Blitline results with AWS Services (like Lambda Functions) instead of an http endpoint. https://t.co/DP6czdYDyo
Tomorrow we are updating out screenshot functionality with the latest libraries, which shouldn't have any effect on your outputs, but we just wanted to give you a heads up to watch your outputs to make sure they are as expected.
Any independent contractors using Blitline interested in having work directed their way for others who wish to convert to using Blitline? Contact [email protected]
π¨Is your company protected from these security vulnerabilities?π¨
Jason Malcolm from @Blitline explains how hackers use Image Processing Systems to attackβand what you can do to stop them.
https://t.co/pKJK0r6v1K