-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
large file missing key ID #422
Comments
Here are two additional observations.
|
The response you are getting from the upload call is based on the response of the server which does not send us the key back, therefore the key value of the response is
|
Excellent, thank you. |
For The same applies to the Thanks. |
With b2sdk-1.24.1,I still see the issue. In my encryption settings provider, a direct subclass of |
@titus8 I cant replicate it. Can you please provide steps how to reproduce it? Thanks. |
I will provide code later today. |
Did the fix in b2sdk-1.24.1 fix an issue with key_id missing from a large file upload? I re-encrypted my large files, and the problem is gone. |
yes |
Well ok, then. Problem fixed. My bad.
… On Sep 29, 2023, at 12:32 AM, Maciej Urbański ***@***.***> wrote:
Closed #422 <#422> as completed.
—
Reply to this email directly, view it on GitHub <#422 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A5HCTP3HH5D7XHAXCAAMKBLX4Z2PXANCNFSM6AAAAAA46V3ETA>.
You are receiving this because you were mentioned.
|
In b2sdk-1.24.0/doc/source/server_side_encryption.rst:
In applications requiring enhanced security, using unique key per file is a good strategy. b2sdk follows a convention,
that makes managing such keys easier:
EncryptionSetting
holds a key identifier, aside from the key itself. This keyidentifier is saved in the metadata of all files uploaded, created or copied via b2sdk methods using
SSE-C
,under
sse_c_key_id
infileInfo
. This allows developers to create key managers that map those ids to keys, storedsecurely in a file or a database.
However, I’m seeing a problem with some files that B2 designates as large, and that are encrypted with SSE-C. The key ID is missing from file_info
{'src_last_modified_millis': '1645044242000', 'large_file_sha1': '8013b77a3b3f5327c88524bcd3ff20fb79affc42'}
and from the encryption setting
<EncryptionSetting(EncryptionMode.SSE_C, EncryptionAlgorithm.AES256, <EncryptionKey(None, None)>)>
Am I missing something here, or is this a bug?
Thanks in advance for your advice. In the meantime, I will investigate further.
The text was updated successfully, but these errors were encountered: