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.

Sign up for GitHub

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

Jump to bottom

AES-GCM key should be sha256(secret)[:32] #86

Closed
aeneasr opened this issue May 31, 2016 · 0 comments
Closed

AES-GCM key should be sha256(secret)[:32] #86

aeneasr opened this issue May 31, 2016 · 0 comments
Assignees
@aeneasr
Labels
breaking change Changes behavior in a breaking manner. feat New feature or request.
Milestone
0.1-beta2

Comments

@aeneasr
Copy link
Member

aeneasr commented May 31, 2016

No description provided.

@aeneasr aeneasr added the feat New feature or request. label May 31, 2016
@aeneasr aeneasr self-assigned this May 31, 2016
@aeneasr aeneasr added this to the 0.1-beta2 milestone Jun 3, 2016
aeneasr pushed a commit that referenced this issue Jun 3, 2016
cli: key is now sha256(secret) #86
1487c33 
* fixed example section in readme
@aeneasr aeneasr added the breaking change Changes behavior in a breaking manner. label Jun 3, 2016
@aeneasr aeneasr mentioned this issue Jun 3, 2016
Merged
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aeneasr aeneasr

Labels
breaking change Changes behavior in a breaking manner. feat New feature or request.
Projects
None yet
Milestone
0.1-beta2
Development

No branches or pull requests
1 participant
@aeneasr