You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The setup.sh script creates a fresh ./secrets/ directory in the root of the repository.
Someone familiar with cryptography probably knows the importance of every file in there, but it's not clear to me which files are necessary for getting back into consul/vault, if any, and how should those files be backed up securely if so.
I guess I'm looking for this information personally, but it might also be helpful added to the README.
Here is the output of all the files in ./secrets/ after running the setup.sh demo:
It would also be extremely helpful to give examples (or short explanations) of how each of these files might be used later on after initially running the setup script.
EDIT: I know this might be common sense to some of you but guarantee this is over a lot of heads.
The
setup.sh
script creates a fresh./secrets/
directory in the root of the repository.Someone familiar with cryptography probably knows the importance of every file in there, but it's not clear to me which files are necessary for getting back into consul/vault, if any, and how should those files be backed up securely if so.
I guess I'm looking for this information personally, but it might also be helpful added to the README.
Here is the output of all the files in
./secrets/
after running thesetup.sh
demo:I've annotated the
_cert()
function to better understand the files involved:I also see that the consul and vault HCL configs end up looking like (respectively):
So I'm just wondering which of these files I need to keep and if/how to keep them under lock and key.
The text was updated successfully, but these errors were encountered: