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

Amazon S3 Client Side Encryption #21

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

Conversation

Andrei-Pozolotin
Copy link

See #20

http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingClientSideEncryption.html

Support for Option 2: Using a Client-Side Master Key:
http://docs.aws.amazon.com/AmazonS3/latest/dev/encrypt-client-side-symmetric-master-key.html

Experimental release on Maven Central, in non Kuali name space:
http://search.maven.org/#artifactdetails%7Ccom.carrotgarden.maven.wagons%7Cmaven-s3-wagon%7C1.2.2-rev001%7Cjar

Master key derivation can use any AES compatible SecretKeyFactory
algorithms with any AES compatible key sizes from the SunJCEProvider:
https://docs.oracle.com/javase/8/docs/technotes/guides/security/SunProviders.html#SunJCEProvider

Example default encryption parameters entry in settings.xml:
<server>
  <id>my.server</id>
  <username>[AWS Access Key ID]</username>
  <password>[AWS Secret Access Key]</password>
  <privateKey>default</privateKey>
  <passphrase>[Encryption Password]</passphrase>
</server>

Example custom encryption parameters entry in settings.xml:
<server>
  <id>my.server</id>
  <username>[AWS Access Key ID]</username>
  <password>[AWS Secret Access Key]</password>
  <privateKey>vers=0;algo=PBKDF2WithHmacSHA1;iter=5000;size=128;salt=A40BC834D695F313</privateKey>
  <passphrase>[Encryption Password]</passphrase>
</server>
@Andrei-Pozolotin Andrei-Pozolotin changed the title Encryption Amazon S3 Client Side Encryption Oct 4, 2015
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.

1 participant