Following up on a previous post about PHP dependency hygiene, the author responds to criticism from Paragon IE (makers of paragonie/sodium_compat) who argued that removing sodium_compat from PHP 7.2+ projects could leave some users vulnerable. The author counters that systems explicitly opting out of ext-sodium are edge cases and that the responsibility for requiring a compat library should fall on those specific systems, not on upstream libraries. The core argument is that sodium_compat was always meant to be a temporary shim, and the PHP community should prefer built-in extensions over PHP-based cryptographic polyfills for better dependency hygiene and security.
1 Comment
Sort: