[#529] Use salt when deriving the encryption key #572
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#572
Loading…
Reference in a new issue
No description provided.
Delete branch "r.loginov/frostfs-s3-gw:feature/529-use_salt_when_deriving_encryption_key"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
close #529
As part of the testing, the following scenarios were performed:
Scenario 1:
Result: it worked correctly.
Scenario 2:
Result: it worked correctly
Scenario 3:
Result: we expect to get an error :
3fa56f2309
tod1812cefc0
I assumed that backwards compatible solution would be uglier when I opened the issue (#529). This one is almost elegant. I like it.
@ -45,0 +70,4 @@
require.Error(t, err)
})
t.Run("wrang private key", func(t *testing.T) {
Typo
wrang
->wrong
?d1812cefc0
to371bbb2128
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
New commits pushed, approval review dismissed automatically according to repository settings
371bbb2128
to0165813b9a
0165813b9a
to4521881800
4521881800
to4d07ff13f7
New commits pushed, approval review dismissed automatically according to repository settings
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.