Skip to content

Feature: File encryption #65

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

Merged
merged 3 commits into from
Mar 1, 2021
Merged

Feature: File encryption #65

merged 3 commits into from
Mar 1, 2021

Conversation

perfectmak
Copy link
Contributor

Description

Adds upload encryption and open file decryption.

Note: This makes a notable change to how daemon used to do encryption, instead of a bucket having a single encryption key for all files, each file now has its own encryption key. And only this key is shared with users when the file is shared.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Unit Test
  • Integration Test

Checklist:

  • My code follows the style guidelines of this project
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Copy link
Contributor

@jsonsivar jsonsivar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

*/
public read8(): number {
const value = this.dataView.getUint8(this.bytePositon);
this.bytePositon += 1;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this not need the endian value?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No it doesn't. Since endianness affects layout of each consecutive byte blocks so a simple 8bit read (1 byte) would always be in the correct order.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it, that makes, thank you. Was wondering if it was by bit 😅

@perfectmak perfectmak force-pushed the feature/file-encryption branch from c9259a4 to 7b9d07c Compare February 28, 2021 23:02
@perfectmak perfectmak merged commit 840fb5f into master Mar 1, 2021
@perfectmak perfectmak deleted the feature/file-encryption branch March 1, 2021 10:21
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.

2 participants