sodium_compat

? Check out Halite: https://paragonie.com/project/halite Want to stop CSRF (including replay attacks)? https://github.com/paragonie/anti-csrf Want to quickly examine the differences between two PHP Archives (e.g. for reproducible builds)? https://github.com/paragonie/pharaoh We even wrote the community's accepted interface for generating cryptographically secure random numbers in PHP 5 projects: https://github.com/paragonie/random_compat And coming soon (pending an audit), a pure-PHP implementation of libsodium that will likely be adopted by WordPress so its automatic updates are Ed25519 secured: https://github.com/paragonie/sodium_compat And even more: https://paragonie.com/projects Guess how many clients we've gotten from all this open source software we wrote over the past two years that demonstrably improves the security posture of software written in PHP? Zero. My solution: Our next project isn't going to be OSS, and it's unlikely that any of our future ones will be unless it's intended to be a giveaway. The open source + consulting business model may sound good in theory, but it simply doesn't work. (Though, I will grant that it's possible that the "consulting about someone else's open source project" is more sustainable, due to near-zero investment in said project itself.)

com/security/advisories A sample of PHP projects I've developed or contributed to significantly: - random_compat - PHP 5 polyfill for the CSPRNG functions introduced in PHP 7; this security library has over 19 million installs according to Packagist - https://github.com/paragonie/random_compat - sodium_compat - A pure-PHP implementation of much of modern elliptic curve cryptography and (AEAD) symmetric encryption - https://github.com/paragonie/sodium_compat - CMS Airship - A secure-by-default content management system - https://paragonie.com/project/airship - CSP-Builder - A developer utility to promote the adoption of Content-Security-Policy headers - https://github.com/paragonie/csp-builder I can be reached via https://paragonie.com/contact or email: security@paragonie.com

ee on this. I'm specifically more concerned with the second-order effect of what you've described; namely, PHP projects can't require ext/libsodium because they can't expect everyone to easily install it. I want to get everyone off mcrypt, unauthenticated AES-CBC, RSA encryption with PKCS1v1.5 padding, etc. I'd like to get Ed25519 signature verification built into automatic updates throughout the entire ecosystem. Sodium_compat was the only reasonable strategy to accomplish these goals, given real-world constraints. > Good thing is that this library will use native libsodium if available, so hopefully the impact of side channels in this isn't that great. I'm hoping there aren't any, but if there are, that installing the PHP extension mitigates them entirely. It'll make it easier to convince $5 hosting platforms to install the extension. :)