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

Adding a completion for $cryptsetup luksChangeKey #380

Merged
merged 3 commits into from
Jan 19, 2020

Conversation

hugoziviani
Copy link
Contributor

Adding a completion for $cryptsetup luksChangeKey

@inconstante
Copy link
Contributor

Hi, Hugo,

thanks for writing this.

From a cryptsetup perspective, the change looks good to me . I would recommend, though, that you write a more descriptive commit message, explaining that luksChangeKey accepts the same arguments as luksAddKey and luksRemoveKey, since they all operate on keys in the luks header.

Also, this pull request seems to address issue #197, so you could add a "Fix #197" sentence to your commit message, so that the associated issue gets closed automatically.

This command accepts the same arguments as luksAddKey and luksRemoveKey and
they all operate on keys in the luks header. 'Fix scop#197'
@scop scop merged commit 5bb526a into scop:master Jan 19, 2020
@scop
Copy link
Owner

scop commented Jan 19, 2020

Thanks @hugoziviani for the code and @gftg85 for the review. Squashed and commit message further tweaked a bit.

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.

None yet

3 participants