Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feasibility check FreeImage to OpenImageIO #324

Open
danoli3 opened this issue Dec 18, 2023 · 1 comment
Open

Feasibility check FreeImage to OpenImageIO #324

danoli3 opened this issue Dec 18, 2023 · 1 comment

Comments

@danoli3
Copy link
Member

danoli3 commented Dec 18, 2023

FreeImage is, unfortunately very slow at updating sub-dependencies which leads to many CVE's exposed and unpatched.

I've tried to keep it up to date but.. easier to just jump into a fresh new ImageIO system.

It's worth checking in future swap out to OpenImageIO or other options
https://github.com/AcademySoftwareFoundation/OpenImageIO

If you are aware of any up to date Image IO systems to evaluate please drop them in here

@danoli3
Copy link
Member Author

danoli3 commented Feb 11, 2024

I've been able to just manually bind separate libraries patched to latest into the FreeImage library so we might be able to continue with FreeImage for a little longer - without compiling the packaged source for those libraries.

Initial Test with LibPNG as many other frameworks/libraries are using it and shared packaged lib made sense.
Especially with the Pegasus disaster we know pngs with payloads to Remote execution, we need these libraries up to date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant