release: v1.1.0 with improved state management, security, and concurrency #41
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.
Summary
This PR finalizes the
v1.1.0
release of SafeBox, delivering major upgrades in lifecycle coordination, cryptographic safety, and multi-threaded performance.Highlights
Lifecycle Management
STARTING
,WRITING
,IDLE
,CLOSED
) to ensure deterministic transitions even under concurrent writes. Prevents invalid state emissions after closure. (#17)SafeBoxGlobalStateObserver
monitors file-level state transitions.SafeBoxStateListener
allows per-instance state tracking.(#12)
Security Hardening
SafeSecretKey
is now XOR-masked using a SHA-256 mask to prevent raw DEK exposure in memory. (#23)AesGcmCipherProvider
now creates ciphers only when needed, minimizing sensitive memory retention. (#28)Cryptographic Concurrency
Cipher
reuse. Supports load-factor-based scaling, ideal for parallelget()
/put()
workloads. (#25)SafeSecretKey
andSecureRandomKeyProvider
now support multi-threaded access via atomic caching. (#26)Stability & Compatibility
ChaCha20
support is missing. Prevents unintentional overrides of external configurations. (#1)Benchmark Update
GitHub Sponsors & Metadata
FUNDING.yml