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

Modify recrypt command to allow recrypting file with different encryp… #232

Conversation

ccojocar
Copy link
Contributor

@ccojocar ccojocar commented Mar 17, 2017

I rebased the PR #211 initially created by @dianac10.

@rnelson0 @nfagerlund Please could you review the changes? We plan to open source soon a plugin for Microsoft KeyVault. Without this fix, we are forced to use a forked version, which we really want to avoid.

cc @brndkfr @maximbaz-microsoft

@ccojocar
Copy link
Contributor Author

@rnelson0 Should we add tests also for this scenario?

@rnelson0
Copy link
Sponsor Member

Yes, tests are definitely recommended.

@ccojocar
Copy link
Contributor Author

ccojocar commented Mar 23, 2017

@rnelson0 I added more tests for recrypt command specifically for the option introduced by this PR. Initially the text is encrypted with PKCS7, then rencrypted with a different encryption plaintext and finally rencrypted back to PKCS7. We introduced the -d (change_encryption) option.

@ccojocar
Copy link
Contributor Author

@rnelson0 Looking forward to you feedback. Do you need more details to be able to review the PR?

@rnelson0
Copy link
Sponsor Member

@cosmincojocar I've reached out to @TomPoulton for some verification. This looks good to me, but we (VP) have just recently accepted this gem so I want to make sure I'm not missing something obvious, and to make sure that the updated tests are properly validating this (I think we need to change the test output so it's more clear which tests are running so we know a test isn't skipped - but unrelated to this PR).

@ccojocar
Copy link
Contributor Author

@rnelson0 Any progress on this PR?

@rnelson0
Copy link
Sponsor Member

rnelson0 commented Apr 3, 2017

I have to rely on @TomPoulton for this, sorry.

@TomPoulton
Copy link
Collaborator

Hi all, from what I can tell by glancing at the logs, it looks like there's an incompatibility between the json_pure v2.0.1 gem and ruby 1.8.7

I imagine we're going to run into these problems more are more, so I suppose we should decide whether we want to "officially" support 1.8.7?

@rnelson0
Copy link
Sponsor Member

@TomPoulton I created #238 for version support. In the meantime, can you review the code itself for possible issues, either technical or that would affect the roadmap?

@ccojocar
Copy link
Contributor Author

@TomPoulton @rnelson0 Any progress with the review? It would be grate if you could merge it if there aren't any concerns.

@ccojocar ccojocar force-pushed the dianac10-modify_recrypt_accept_different_input_output branch from 58a25d1 to 4698024 Compare July 10, 2017 08:11
@ccojocar
Copy link
Contributor Author

@rnelson0 Also this branch is rebased.

@rnelson0
Copy link
Sponsor Member

@cosmincojocar This should be good to rebase again, as well!

@ccojocar ccojocar force-pushed the dianac10-modify_recrypt_accept_different_input_output branch from 4698024 to 82fbe23 Compare July 12, 2017 07:33
@ccojocar
Copy link
Contributor Author

@rnelson0 done, the tests are now green.

@rnelson0
Copy link
Sponsor Member

Hooray! Thanks for your patience!

@rnelson0 rnelson0 merged commit b255ba0 into voxpupuli:master Jul 12, 2017
@kevgreen-ebay-com
Copy link

Personal, rather than company opinion, but it is possible that the way this is implemented has broken GPG encryption causing the default to always be PKCS7 on recrypt, irrespective of what is listed in the various config files. It certainly appears that 3.0.0 onwards is affected by this problem.

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

4 participants