discussing security ideas

[coder7695]

Hello,

The libwebp library is listed as in scope project for google patch rewards. I am individual  contributor interested in improving security of the project. 

I wanted to discuss potential security improvements which might align well with the patch rewards program https://bughunters.google.com/about/rules/open-source/patch-rewards-program-rules

Some of the ideas mentioned in the link include

• Adopting the Safe Buffers Programming Model to migrate from C-style buffers to C++ containers, including the use of -Wunsafe-buffer-usage to prevent backsliding
• Replacing C++ dependencies processing potentially untrusted inputs with equivalent Rust dependencies
• Building the scaffolding to enable writing new components in Rust, and demonstrating this capability by adding one feature in Rust
• Elimination of error-prone design patterns or library calls
• Rust <> C++ Bindings through the use of manual bindings or interop tooling such as bindgen, cbindgen, and cxx; with accurate safety comments
• Refactoring Rust crates to minimize or eliminate unsafe code
• Improving the auditability and verifiability of Rust crates that use unsafe code, such as by encapsulating unsafe blocks within self-contained, safe abstractions
• Please comment on which of them would be relevant for the project maintainers. 

Thanks

GitHub Project: https://github.com/coder7695

Sent with Proton Mail secure email.