-
Notifications
You must be signed in to change notification settings - Fork 42
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
secret was encrypted with newer version error #23
Comments
Hi.
|
Hi, Thanks for the quick reply, I figured out the issue; it happens when I add the encrypted file to my gitlab repository:
Something happens with the file, the MD5 hash of the locally created file and git cloned file are different. Not sure what git(lab) does and if this also happens with github.
|
Here is an example btw:
When you kubesec encrypt this, commit it to a repo, then pull it to another folder then you can't decrypt it anymore. Perhaps this is a git issue with very long lines? |
Any chance you have .gitattributes with newline normalization? https://help.github.com/en/articles/dealing-with-line-endings |
I don't have one, I did use kubesec on Windows. Should I try it? |
I've encounted same issue, and it was caused via EOL. I can avoid issue with change file eol to LF and use .gitattributes to specify file EOL. |
I use the latest version of kubesec but see this message when decrypting a secret that I encrypted previously on another machine:
I'm using the latest version though:
I'm using AWS KMS. Any idea how to troubleshoot this?
The text was updated successfully, but these errors were encountered: