From e7b7a6a836df7faa50b5130e0a54271fff9fe59b Mon Sep 17 00:00:00 2001 From: Jean-Paul Calderone Date: Wed, 3 Apr 2019 14:00:26 -0400 Subject: [PATCH] Try using -pass instead of -k --- .circleci/config.yml | 6 +++--- .circleci/secret-env-cipher | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/.circleci/config.yml b/.circleci/config.yml index babd552ab..54f6cb77a 100644 --- a/.circleci/config.yml +++ b/.circleci/config.yml @@ -449,7 +449,7 @@ jobs: command: | # If you create an encryption key like this: # - # openssl enc -aes-256-cbc -k secret -P -md sha1 + # openssl enc -aes-256-cbc -k secret -P -md sha256 # From the output that looks like: # @@ -462,7 +462,7 @@ jobs: # then you can re-generate ``secret-env-cipher`` locally using the # command: # - # openssl aes-256-cbc -e -in secret-env-plain -out .circleci/secret-env-cipher -k $KEY + # openssl aes-256-cbc -e -in secret-env-plain -out .circleci/secret-env-cipher -pass env:KEY # # Make sure the key is set as the KEY environment variable in the # CircleCI web interface. You can do this by visiting @@ -474,7 +474,7 @@ jobs: # change and re-encrypt it) like just like CircleCI recovers it # here: # - openssl aes-256-cbc -d -in .circleci/secret-env-cipher -k $KEY >> ~/secret-environment + openssl aes-256-cbc -d -in .circleci/secret-env-cipher -pass env:KEY >> ~/secret-environment # Now get it into the process environment. . ~/secret-environment diff --git a/.circleci/secret-env-cipher b/.circleci/secret-env-cipher index 90471b25f..e56fe8d63 100644 --- a/.circleci/secret-env-cipher +++ b/.circleci/secret-env-cipher @@ -1 +1 @@ -Salted__*Xx=Z9Ypۮ$Y^P2 -Mk}\ | 3ܓY ~BxBC*ݸ0" \ No newline at end of file +Salted__YvعyjS<֨$7U`Gt,Lt?&ic.7}MX~s'\