-
Notifications
You must be signed in to change notification settings - Fork 17
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
docs: detail on integrity checks #65
Comments
Lightning Stream uses https://github.com/PowerDNS/simpleblob for object storage, which uses https://github.com/minio/minio-go for S3 storage. |
Sure, I looked briefly through that code yesterday. However you need to explicitly set the MD5 option in the Sending Content-MD5 is highly recommended, because otherwise the receiving S3 service has no way of ensuring integrity. With Content-MD5, the S3 service caluclates MD5 and compares it against the MD5 provided in Content-MD5, and so you therefore have a high level of confidence that what you uploaded is what was stored. |
Thanks, I added PowerDNS/simpleblob#49 for this and added it to the next patch release milestone. |
Thanks @wojas ! |
Looking through the codebase, it looks like
lightningstream
does not use theContent-MD5
header in S3-compatible APIs in order to ensure end-to-end integrity of blobs uploaded.It would be nice to have a couple of paragraphs in the docs as to how
lightningstream
approaches this.The text was updated successfully, but these errors were encountered: