Vault plugins#84452
Conversation
|
The test The test The test |
|
@bcoca does this need to be marked with “unimportant CI”? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@webknjaz yes, TIL ... now off to abuse the label! |
|
@bcoca yeah, I think I suggested this label last year or so, to facilitate WIP PRs / experiment draft not getting into our CI maintenance queues... |
9d09c59 to
f8ba7d1
Compare
|
The test The test The test The test The test The test |
To deal with issues with current AES256 cipher we
changed a bit how ciphers are loaded to enabled a
simpler way to update/upgrade ciphers going forward
* We now validate vault parameters to avoid injection
* Added new config to set vault cipher used for encryption
* Ciphers are now used as classes instead of objects
* Implemented 'cipher loader' to encapsulate and simplify
dealing with mulitple ciphers
* New ciphers added, kept aes256 for backwards compat
* New ciphers used base64 armor over hexlify
* Updated tests to be more cipher agonstic and/or use dummy cipher
minimize new API surface area
* cut down cipher implementation size
* add basic testing framework
* fix tests
move vault-id validation to format_vaulttext_envelope
* update/optimize tests
* minimize delta for backport
enable use of vault plugins
fixes, docs and simplification
draft gpg vault (most likely punt to coll)
Co-authored-by: Abhijeet Kasurde <akasurde@redhat.com>
|
The test The test The test The test The test |
my current PoI
ISSUE TYPE