mirror of
https://github.com/nspcc-dev/neofs-s3-gw.git
synced 2026-03-01 04:29:15 +00:00
Support encryption #92
Labels
No labels
I2
I2
I3
I4
S2
S3
S4
S4
U0
U1
U2
U2
U3
U4
U4
auth-mate
blocked
bug
config
dependencies
discussion
documentation
enhancement
epic
feature
go
good first issue
help wanted
performance
question
security
test
tree-service
tree-service
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-s3-gw#92
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @KirillovDenis on GitHub (Aug 5, 2021).
Should s3-gw support encryption?
@realloc commented on GitHub (Aug 11, 2021):
Yes, but we need to figure out the details. I doubt it could work properly in public network, so we could start with some private|local key management services integration. Let's wait a little to survey the possible use cases.
@alexvanin commented on GitHub (Sep 9, 2021):
As for public networks, encryption should be done completely on client side, before object upload.
@alexvanin commented on GitHub (Jun 23, 2022):
Consider having KMS service and binding it with S3 Gateway.