Isolate and authenticate persistent object caches - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
WordPress persistent-cache namespaces and signing keys now include project/environment identity. The default temporary directory is private per user and namespace; an explicit prefix remains a readable label but cannot accidentally share values between sites.
Filesystem, SQLite/PDO and APCu adapters use an authenticated marshaller before decoding, alongside the existing native signed Redis/Memcached codec. Persistent initialization requires a strong independent cache/application secret; unsafe configuration falls back to request memory. Framework container compilation also validates its application secret. Prepare patch 1.0.3.
Validation: CS/PHPStan and the complete Framework suite with enabled APCu plus isolated Redis/Memcached passed (58 tests/340 assertions, no skips). Live native backend smoke passed 3 tests/37 assertions; runtime container and lint checks passed. No existing backend was flushed. APCu still requires trusted PHP pools/writers because its extension can deserialize objects stored directly by another PHP writer before userland marshalling.