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
In pillar.example there are example how to read keys from state files:
ssh_keys:
# or you can provide path to key on Salt fileserverprivkey: salt://path_to_PRIVATEKEYpubkey: salt://path_to_PUBLICKEY
But storing private keys in state files is insecure, for example here is recommendation to not do this.
And most of users will follow that example, without understanding the security risks when store private keys as files into state storage.
Also filling long private key text inside yaml is not good solution too, because operating with separate files is much more universal (eg for regenerating, reusing in other scripts).
Describe the solution you'd like
For solve this problem will be good to implement reading contents if ssh keys from file inside pillar structure.
Here is feature request about build-in support for this in SaltStack, so we could use something like this:
ssh_keys:
# or you can provide path to key on Salt fileserverprivkey: pillar://path_to_PRIVATEKEYpubkey: pillar://path_to_PUBLICKEY
but it is closed with recommendation to use salt.pillar.file_tree, that isn't suitable for current task.
So, is it possible to implement this feature in users-formula itself? Or maybe you can provide some workaround for this?
certificates:
'www.example.com':
# choose one of: deploying this cert by pillar (e.g. in combination with# ext_pillar and file_tree)# public_cert_pillar: certs:example.com:fullchain.pem# private_key_pillar: certs:example.com:privkey.pem
Is your feature request related to a problem?
In pillar.example there are example how to read keys from state files:
But storing private keys in state files is insecure, for example here is recommendation to not do this.
And most of users will follow that example, without understanding the security risks when store private keys as files into state storage.
Also filling long private key text inside
yaml
is not good solution too, because operating with separate files is much more universal (eg for regenerating, reusing in other scripts).Describe the solution you'd like
For solve this problem will be good to implement reading contents if ssh keys from file inside pillar structure.
Here is feature request about build-in support for this in SaltStack, so we could use something like this:
but it is closed with recommendation to use salt.pillar.file_tree, that isn't suitable for current task.
So, is it possible to implement this feature in users-formula itself? Or maybe you can provide some workaround for this?
Describe alternatives you've considered
Some alternatives are provided in issues saltstack/salt#18406, saltstack/salt#3790 and saltstack/salt#1543 but they isn't good.
The text was updated successfully, but these errors were encountered: