SecHub data encryption #3250 #3254
Draft
Conversation
This file contains 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
de-jcup
changed the title
- moved own encryption implementations into own gradle sub module "sechub-encryption" - CryptoAccess class is kept in commons-core because there are no dependencies to bouncy castle or other libraries - updated bouncy castle dependencies to 1.78.1
de-jcup
force-pushed
the
feature-3250-encrypt-sechub-database-content
branch
2 times, most recently
from
ebbd23a
to
06c611a
Compare
- refactoring - usage tests introduced - renamed library to sechub-commons-encryption
de-jcup
force-pushed
the
feature-3250-encrypt-sechub-database-content
branch
3 times, most recently
from
0cc1637
to
6a4b7dd
Compare
- introduce schedule encryption service and other classes used at startup time and for encryption - restrict access and storage, avoid using configuration when not absolut necessary - created dedicated job message which contains unencrypted configuration at runtime. Only one message uses this one -> clear not accidently used on another code location - created migration scripts, seperated pool id generation for h2 and postgres because of binary type. Also postgres will migrate old data automatically to NoneCipher variant (means no real encryption, but admin will be able to rotate keys...) - because of separation I moved the common sql scripts to dedicated folder (to avoid subfolder problems in flyway execution) - enhanced unit tests + changed to junit5 - updated encryption concept documentation - marked old unencrypted parts as deprecated - job info for user uses decryption to provide meta data for users - admin job info no longer contain config - scan logs no longer contain config - fixed gradle sub module naming problem
de-jcup
force-pushed
the
feature-3250-encrypt-sechub-database-content
branch
from
6a4b7dd
to
5948961
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR
handles encryption library
sechub-encryptionand move encryption implementations to this library #3273sechub-encryption#3275Handles encryption of SecHub configuration
after all