data protection follow up #626
Draft
+4,815
−172
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
unixslayer
force-pushed
the
data-protection
branch
from
2773784 to
a99d724
Compare
- remove defuse legacy as it does not apply
unixslayer
force-pushed
the
data-protection
branch
from
a99d724 to
abd7bf5
Compare
emphasize on message protection
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.
Why is this change proposed?
This is series of follow up commits to Data Protection module
Description of Changes
defuse/php-ancryptionas internal package adapting Ecotone coding standardsPull Request Contribution Terms