Skip to content
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

Enable server-side encryption for S3. #111

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

barboni
Copy link

@barboni barboni commented Jun 21, 2015

Solves issue #75.

Review on Reviewable

@benjamin79
Copy link

@barboni How would i tell s3 the key when downloading? At the moment i use the url.
Is there a reason this hasn´t been merged?

@gsuess
Copy link
Contributor

gsuess commented Jul 31, 2015

@benjamin79 The only reason I didn't merge it yet, is because I didn't have the time to review it yet. It is on my TODO list though

@barboni
Copy link
Author

barboni commented Jul 31, 2015

@benjamin79 You have to set the following three headers accordingly: x-amz-server-side-encryption-customer-key, x-amz-server-side-encryption-customer-key-MD5, x-amz-server-side-encryption-customer-algorithm. Here's a snippet to help you out: https://gist.github.com/barboni/4c64b6e0895aafd9e7c0

@meonkeys
Copy link

meonkeys commented Dec 4, 2015

Patch looks fine, IMHO. @benjamin79 , will you please merge?

@iameli
Copy link

iameli commented Dec 9, 2015

This is actually broken because the sse key isn't in the directiveMatch schema. (Possibly that didn't exist when the PR was first opened?)

I'll be opening another PR with a correction shortly.

@iameli
Copy link

iameli commented Dec 10, 2015

Disregard my last message, I misinterpreted how this works. Just tested this out, LGTM.

@ggn06awu
Copy link

Can we please look to accept this PR? Seems like a straightforward yet important addition to Slingshot!

@mccambridge
Copy link

+1 This seems like a simple fix. We really need this functionality, too.

@mccambridge
Copy link

@gsuess Was geht jetzt mit dieser PR?

@barboni
Copy link
Author

barboni commented Apr 12, 2016

Two more months and the PR is one year old. Yay!

@mccambridge
Copy link

I'm wondering if the thing to do is fork this repo and take it over. Not sure I want to, but it's an idea.

@Cu4rach4
Copy link

Work excelent, but on google chrome is not active AES256 on S3 file, but in safari is working...didnt know why!

@michaelrokosh
Copy link

@gsuess Could you review this PR?

@hrdymchl
Copy link

hrdymchl commented Aug 2, 2016

Would love to see this happen. This added functionality is crucial to enterprise applications that require the added security.

@chris-jamieson
Copy link

+1 this is a great feature and a shame not to have it included in slingshot - I am about to roll my own version of this for my app and would have been nice to just use Slingshot!

chris-jamieson added a commit to chris-jamieson/meteor-slingshot that referenced this pull request Sep 2, 2016
@chris-jamieson
Copy link

In case it's helpful for anyone, I ended up merging this PR into the latest version of the package and put it up on Atmosphere: https://atmospherejs.com/jamiesoncj/slingshot - sorry for creating one more atmosphere package rather than waiting for this PR to get merged in, but I just needed this functionality.

@michaelcbrook
Copy link

+1 Please pull. This package is virtually useless without encryption for me. I have multiple projects that require it, and this package is the most secure and efficient way to handle file uploads on S3 so far. But setting the encryption flag is a must.

@hasantayyar
Copy link

This can be merged. @gsuess did you have time to review?

@bliles
Copy link

bliles commented Jun 1, 2017

Just adding another voice that this patch is crucial for my project and I would love to see it included in the main Slingshot package.

@HemalR
Copy link

HemalR commented Sep 23, 2017

@jamiesoncj

Are you still successfully using your package? Found this when trying to figure out this functionality...

Also, just to confirm, it seems a near drop in replacement (with regards to the package API's and how things work). Is this correct?

Update

Tried it as a drop in replacement and seems to be working great, thank you!

@chris-jamieson
Copy link

@HemalR sorry for slow reply - but looks like you tried it and it's working so 👍 😄

@HemalR
Copy link

HemalR commented Sep 26, 2017

No worries mate, thanks for doing the work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.