2015-04-20 03:31:44 +00:00
|
|
|
# (c) 2014, James Tanner <tanner.jc@gmail.com>
|
|
|
|
#
|
|
|
|
# Ansible is free software: you can redistribute it and/or modify
|
|
|
|
# it under the terms of the GNU General Public License as published by
|
|
|
|
# the Free Software Foundation, either version 3 of the License, or
|
|
|
|
# (at your option) any later version.
|
|
|
|
#
|
|
|
|
# Ansible is distributed in the hope that it will be useful,
|
|
|
|
# but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
# GNU General Public License for more details.
|
|
|
|
#
|
|
|
|
# You should have received a copy of the GNU General Public License
|
|
|
|
# along with Ansible. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
#
|
|
|
|
# ansible-vault is a script that encrypts/decrypts YAML files. See
|
|
|
|
# http://docs.ansible.com/playbooks_vault.html for more details.
|
|
|
|
|
2015-10-20 01:36:19 +00:00
|
|
|
from __future__ import (absolute_import, division, print_function)
|
|
|
|
__metaclass__ = type
|
|
|
|
|
2015-04-20 03:31:44 +00:00
|
|
|
import os
|
|
|
|
import sys
|
|
|
|
|
2017-06-02 11:14:11 +00:00
|
|
|
from ansible.cli import CLI
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
from ansible.errors import AnsibleOptionsError
|
2017-06-02 11:14:11 +00:00
|
|
|
from ansible.module_utils._text import to_text, to_bytes
|
2015-10-26 21:23:09 +00:00
|
|
|
from ansible.parsing.dataloader import DataLoader
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
from ansible.parsing.vault import VaultEditor, VaultLib, match_encrypt_secret
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-11-10 19:40:55 +00:00
|
|
|
try:
|
|
|
|
from __main__ import display
|
|
|
|
except ImportError:
|
|
|
|
from ansible.utils.display import Display
|
|
|
|
display = Display()
|
|
|
|
|
|
|
|
|
2015-04-30 22:43:53 +00:00
|
|
|
class VaultCLI(CLI):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' can encrypt any structured data file used by Ansible.
|
|
|
|
This can include *group_vars/* or *host_vars/* inventory variables,
|
|
|
|
variables loaded by *include_vars* or *vars_files*, or variable files
|
|
|
|
passed on the ansible-playbook command line with *-e @file.yml* or *-e @file.json*.
|
|
|
|
Role variables and defaults are also included!
|
|
|
|
|
2017-03-24 19:05:25 +00:00
|
|
|
Because Ansible tasks, handlers, and other objects are data, these can also be encrypted with vault.
|
|
|
|
If you'd like to not expose what variables you are using, you can keep an individual task file entirely encrypted.
|
2017-03-23 05:11:40 +00:00
|
|
|
|
|
|
|
The password used with vault currently must be the same for all files you wish to use together at the same time.
|
|
|
|
'''
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-02-17 15:12:14 +00:00
|
|
|
VALID_ACTIONS = ("create", "decrypt", "edit", "encrypt", "encrypt_string", "rekey", "view")
|
|
|
|
|
|
|
|
FROM_STDIN = "stdin"
|
|
|
|
FROM_ARGS = "the command line args"
|
|
|
|
FROM_PROMPT = "the interactive prompt"
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-11-10 19:40:55 +00:00
|
|
|
def __init__(self, args):
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-03-07 20:30:09 +00:00
|
|
|
self.b_vault_pass = None
|
|
|
|
self.b_new_vault_pass = None
|
2017-02-17 15:12:14 +00:00
|
|
|
self.encrypt_string_read_stdin = False
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
|
|
|
|
self.encrypt_secret = None
|
|
|
|
self.encrypt_vault_id = None
|
|
|
|
self.new_encrypt_secret = None
|
|
|
|
self.new_encrypt_vault_id = None
|
|
|
|
|
2015-11-10 19:40:55 +00:00
|
|
|
super(VaultCLI, self).__init__(args)
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-03-23 05:11:40 +00:00
|
|
|
def set_action(self):
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-03-23 05:11:40 +00:00
|
|
|
super(VaultCLI, self).set_action()
|
2015-04-27 11:31:41 +00:00
|
|
|
|
|
|
|
# options specific to self.actions
|
|
|
|
if self.action == "create":
|
|
|
|
self.parser.set_usage("usage: %prog create [options] file_name")
|
|
|
|
elif self.action == "decrypt":
|
|
|
|
self.parser.set_usage("usage: %prog decrypt [options] file_name")
|
|
|
|
elif self.action == "edit":
|
|
|
|
self.parser.set_usage("usage: %prog edit [options] file_name")
|
|
|
|
elif self.action == "view":
|
|
|
|
self.parser.set_usage("usage: %prog view [options] file_name")
|
|
|
|
elif self.action == "encrypt":
|
|
|
|
self.parser.set_usage("usage: %prog encrypt [options] file_name")
|
2017-02-17 15:12:14 +00:00
|
|
|
# I have no prefence for either dash or underscore
|
|
|
|
elif self.action == "encrypt_string":
|
|
|
|
self.parser.add_option('-p', '--prompt', dest='encrypt_string_prompt',
|
|
|
|
action='store_true',
|
|
|
|
help="Prompt for the string to encrypt")
|
|
|
|
self.parser.add_option('-n', '--name', dest='encrypt_string_names',
|
|
|
|
action='append',
|
|
|
|
help="Specify the variable name")
|
|
|
|
self.parser.add_option('--stdin-name', dest='encrypt_string_stdin_name',
|
|
|
|
default=None,
|
|
|
|
help="Specify the variable name for stdin")
|
|
|
|
self.parser.set_usage("usage: %prog encrypt-string [--prompt] [options] string_to_encrypt")
|
2015-07-14 14:10:03 +00:00
|
|
|
elif self.action == "rekey":
|
2015-04-27 11:31:41 +00:00
|
|
|
self.parser.set_usage("usage: %prog rekey [options] file_name")
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-03-23 05:11:40 +00:00
|
|
|
def parse(self):
|
|
|
|
|
|
|
|
self.parser = CLI.base_parser(
|
|
|
|
vault_opts=True,
|
2017-06-02 11:14:11 +00:00
|
|
|
usage="usage: %%prog [%s] [options] [vaultfile.yml]" % "|".join(self.VALID_ACTIONS),
|
2017-06-21 04:18:40 +00:00
|
|
|
desc="encryption/decryption utility for Ansible data files",
|
2017-06-02 11:14:11 +00:00
|
|
|
epilog="\nSee '%s <command> --help' for more information on a specific command.\n\n" % os.path.basename(sys.argv[0])
|
2017-03-23 05:11:40 +00:00
|
|
|
)
|
|
|
|
|
|
|
|
self.set_action()
|
|
|
|
|
2016-09-29 21:14:02 +00:00
|
|
|
super(VaultCLI, self).parse()
|
|
|
|
|
2015-11-10 19:40:55 +00:00
|
|
|
display.verbosity = self.options.verbosity
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-02-17 15:12:14 +00:00
|
|
|
can_output = ['encrypt', 'decrypt', 'encrypt_string']
|
2015-08-27 00:59:02 +00:00
|
|
|
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
if self.options.vault_ids:
|
|
|
|
for vault_id in self.options.vault_ids:
|
|
|
|
if u';' in vault_id:
|
|
|
|
raise AnsibleOptionsError("'%s' is not a valid vault id. The character ';' is not allowed in vault ids" % vault_id)
|
|
|
|
|
2015-08-27 00:59:02 +00:00
|
|
|
if self.action not in can_output:
|
|
|
|
if self.options.output_file:
|
|
|
|
raise AnsibleOptionsError("The --output option can be used only with ansible-vault %s" % '/'.join(can_output))
|
|
|
|
if len(self.args) == 0:
|
|
|
|
raise AnsibleOptionsError("Vault requires at least one filename as a parameter")
|
|
|
|
else:
|
2015-08-26 17:21:20 +00:00
|
|
|
# This restriction should remain in place until it's possible to
|
|
|
|
# load multiple YAML records from a single file, or it's too easy
|
|
|
|
# to create an encrypted file that can't be read back in. But in
|
|
|
|
# the meanwhile, "cat a b c|ansible-vault encrypt --output x" is
|
|
|
|
# a workaround.
|
2015-08-27 00:59:02 +00:00
|
|
|
if self.options.output_file and len(self.args) > 1:
|
2015-08-26 17:21:20 +00:00
|
|
|
raise AnsibleOptionsError("At most one input file may be used with the --output option")
|
|
|
|
|
2017-02-20 16:38:41 +00:00
|
|
|
if self.action == 'encrypt_string':
|
|
|
|
if '-' in self.args or len(self.args) == 0 or self.options.encrypt_string_stdin_name:
|
|
|
|
self.encrypt_string_read_stdin = True
|
|
|
|
|
|
|
|
# TODO: prompting from stdin and reading from stdin seem
|
|
|
|
# mutually exclusive, but verify that.
|
|
|
|
if self.options.encrypt_string_prompt and self.encrypt_string_read_stdin:
|
|
|
|
raise AnsibleOptionsError('The --prompt option is not supported if also reading input from stdin')
|
2017-02-17 15:12:14 +00:00
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
def run(self):
|
2015-07-04 14:23:30 +00:00
|
|
|
super(VaultCLI, self).run()
|
2015-09-09 20:33:52 +00:00
|
|
|
loader = DataLoader()
|
2015-07-04 14:23:30 +00:00
|
|
|
|
2015-10-31 17:56:14 +00:00
|
|
|
# set default restrictive umask
|
|
|
|
old_umask = os.umask(0o077)
|
|
|
|
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
vault_ids = self.options.vault_ids
|
|
|
|
|
|
|
|
# there are 3 types of actions, those that just 'read' (decrypt, view) and only
|
|
|
|
# need to ask for a password once, and those that 'write' (create, encrypt) that
|
|
|
|
# ask for a new password and confirm it, and 'read/write (rekey) that asks for the
|
|
|
|
# old password, then asks for a new one and confirms it.
|
|
|
|
|
|
|
|
# TODO: instead of prompting for these before, we could let VaultEditor
|
|
|
|
# call a callback when it needs it.
|
|
|
|
if self.action in ['decrypt', 'view', 'rekey']:
|
|
|
|
vault_secrets = self.setup_vault_secrets(loader,
|
|
|
|
vault_ids=vault_ids,
|
|
|
|
vault_password_files=self.options.vault_password_files,
|
|
|
|
ask_vault_pass=self.options.ask_vault_pass)
|
|
|
|
|
|
|
|
if not vault_secrets:
|
|
|
|
raise AnsibleOptionsError("A vault password is required to use Ansible's Vault")
|
|
|
|
|
|
|
|
if self.action in ['encrypt', 'encrypt_string', 'create', 'edit']:
|
|
|
|
if len(vault_ids) > 1:
|
|
|
|
raise AnsibleOptionsError("Only one --vault-id can be used for encryption")
|
|
|
|
|
|
|
|
vault_secrets = None
|
|
|
|
vault_secrets = \
|
|
|
|
self.setup_vault_secrets(loader,
|
|
|
|
vault_ids=vault_ids,
|
|
|
|
vault_password_files=self.options.vault_password_files,
|
|
|
|
ask_vault_pass=self.options.ask_vault_pass,
|
|
|
|
create_new_password=True)
|
|
|
|
|
|
|
|
if not vault_secrets:
|
|
|
|
raise AnsibleOptionsError("A vault password is required to use Ansible's Vault")
|
|
|
|
|
|
|
|
encrypt_secret = match_encrypt_secret(vault_secrets)
|
|
|
|
# only one secret for encrypt for now, use the first vault_id and use its first secret
|
|
|
|
# self.encrypt_vault_id = list(vault_secrets.keys())[0]
|
|
|
|
# self.encrypt_secret = vault_secrets[self.encrypt_vault_id][0]
|
|
|
|
self.encrypt_vault_id = encrypt_secret[0]
|
|
|
|
self.encrypt_secret = encrypt_secret[1]
|
|
|
|
|
|
|
|
if self.action in ['rekey']:
|
|
|
|
new_vault_ids = []
|
|
|
|
if self.options.new_vault_id:
|
|
|
|
new_vault_ids.append(self.options.new_vault_id)
|
|
|
|
|
|
|
|
new_vault_secrets = \
|
|
|
|
self.setup_vault_secrets(loader,
|
|
|
|
vault_ids=new_vault_ids,
|
|
|
|
vault_password_files=self.options.new_vault_password_files,
|
|
|
|
ask_vault_pass=self.options.ask_vault_pass,
|
|
|
|
create_new_password=True)
|
|
|
|
|
|
|
|
if not new_vault_secrets:
|
|
|
|
raise AnsibleOptionsError("A new vault password is required to use Ansible's Vault rekey")
|
|
|
|
|
|
|
|
# There is only one new_vault_id currently and one new_vault_secret
|
|
|
|
new_encrypt_secret = match_encrypt_secret(new_vault_secrets)
|
|
|
|
|
|
|
|
self.new_encrypt_vault_id = new_encrypt_secret[0]
|
|
|
|
self.new_encrypt_secret = new_encrypt_secret[1]
|
|
|
|
|
|
|
|
loader.set_vault_secrets(vault_secrets)
|
|
|
|
|
|
|
|
# FIXME: do we need to create VaultEditor here? its not reused
|
2017-08-08 20:10:03 +00:00
|
|
|
vault = VaultLib(vault_secrets)
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
self.editor = VaultEditor(vault)
|
2015-08-26 13:47:37 +00:00
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
self.execute()
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-10-31 17:56:14 +00:00
|
|
|
# and restore umask
|
|
|
|
os.umask(old_umask)
|
|
|
|
|
2015-08-26 17:21:20 +00:00
|
|
|
def execute_encrypt(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' encrypt the supplied file using the provided vault secret '''
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-08-27 07:07:42 +00:00
|
|
|
if len(self.args) == 0 and sys.stdin.isatty():
|
2015-11-10 19:40:55 +00:00
|
|
|
display.display("Reading plaintext input from stdin", stderr=True)
|
2015-08-27 07:07:42 +00:00
|
|
|
|
2015-08-26 17:21:20 +00:00
|
|
|
for f in self.args or ['-']:
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
# Fixme: use the correct vau
|
|
|
|
self.editor.encrypt_file(f, self.encrypt_secret,
|
|
|
|
vault_id=self.encrypt_vault_id,
|
|
|
|
output_file=self.options.output_file)
|
2015-08-22 14:17:15 +00:00
|
|
|
|
2015-08-27 07:07:42 +00:00
|
|
|
if sys.stdout.isatty():
|
2015-11-10 19:40:55 +00:00
|
|
|
display.display("Encryption successful", stderr=True)
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2017-02-17 15:12:14 +00:00
|
|
|
def format_ciphertext_yaml(self, b_ciphertext, indent=None, name=None):
|
|
|
|
indent = indent or 10
|
|
|
|
|
|
|
|
block_format_var_name = ""
|
|
|
|
if name:
|
|
|
|
block_format_var_name = "%s: " % name
|
|
|
|
|
2017-03-03 16:37:27 +00:00
|
|
|
block_format_header = "%s!vault |" % block_format_var_name
|
2017-02-17 15:12:14 +00:00
|
|
|
lines = []
|
|
|
|
vault_ciphertext = to_text(b_ciphertext)
|
|
|
|
|
|
|
|
lines.append(block_format_header)
|
|
|
|
for line in vault_ciphertext.splitlines():
|
|
|
|
lines.append('%s%s' % (' ' * indent, line))
|
|
|
|
|
|
|
|
yaml_ciphertext = '\n'.join(lines)
|
|
|
|
return yaml_ciphertext
|
|
|
|
|
|
|
|
def execute_encrypt_string(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' encrypt the supplied string using the provided vault secret '''
|
2017-02-17 15:12:14 +00:00
|
|
|
b_plaintext = None
|
|
|
|
|
|
|
|
# Holds tuples (the_text, the_source_of_the_string, the variable name if its provided).
|
|
|
|
b_plaintext_list = []
|
|
|
|
|
|
|
|
# remove the non-option '-' arg (used to indicate 'read from stdin') from the candidate args so
|
2017-06-12 06:55:19 +00:00
|
|
|
# we don't add it to the plaintext list
|
2017-02-17 15:12:14 +00:00
|
|
|
args = [x for x in self.args if x != '-']
|
|
|
|
|
|
|
|
# We can prompt and read input, or read from stdin, but not both.
|
|
|
|
if self.options.encrypt_string_prompt:
|
|
|
|
msg = "String to encrypt: "
|
|
|
|
|
|
|
|
name = None
|
|
|
|
name_prompt_response = display.prompt('Variable name (enter for no name): ')
|
|
|
|
|
|
|
|
# TODO: enforce var naming rules?
|
|
|
|
if name_prompt_response != "":
|
|
|
|
name = name_prompt_response
|
|
|
|
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
# TODO: could prompt for which vault_id to use for each plaintext string
|
|
|
|
# currently, it will just be the default
|
2017-02-17 15:12:14 +00:00
|
|
|
# could use private=True for shadowed input if useful
|
|
|
|
prompt_response = display.prompt(msg)
|
|
|
|
|
|
|
|
if prompt_response == '':
|
|
|
|
raise AnsibleOptionsError('The plaintext provided from the prompt was empty, not encrypting')
|
|
|
|
|
|
|
|
b_plaintext = to_bytes(prompt_response)
|
|
|
|
b_plaintext_list.append((b_plaintext, self.FROM_PROMPT, name))
|
|
|
|
|
|
|
|
# read from stdin
|
|
|
|
if self.encrypt_string_read_stdin:
|
|
|
|
if sys.stdout.isatty():
|
|
|
|
display.display("Reading plaintext input from stdin. (ctrl-d to end input)", stderr=True)
|
|
|
|
|
|
|
|
stdin_text = sys.stdin.read()
|
|
|
|
if stdin_text == '':
|
|
|
|
raise AnsibleOptionsError('stdin was empty, not encrypting')
|
|
|
|
|
|
|
|
b_plaintext = to_bytes(stdin_text)
|
|
|
|
|
|
|
|
# defaults to None
|
|
|
|
name = self.options.encrypt_string_stdin_name
|
|
|
|
b_plaintext_list.append((b_plaintext, self.FROM_STDIN, name))
|
|
|
|
|
|
|
|
# use any leftover args as strings to encrypt
|
|
|
|
# Try to match args up to --name options
|
|
|
|
if hasattr(self.options, 'encrypt_string_names') and self.options.encrypt_string_names:
|
2017-02-21 15:30:21 +00:00
|
|
|
name_and_text_list = list(zip(self.options.encrypt_string_names, args))
|
2017-02-17 15:12:14 +00:00
|
|
|
|
|
|
|
# Some but not enough --name's to name each var
|
|
|
|
if len(args) > len(name_and_text_list):
|
|
|
|
# Trying to avoid ever showing the plaintext in the output, so this warning is vague to avoid that.
|
|
|
|
display.display('The number of --name options do not match the number of args.',
|
|
|
|
stderr=True)
|
|
|
|
display.display('The last named variable will be "%s". The rest will not have names.' % self.options.encrypt_string_names[-1],
|
|
|
|
stderr=True)
|
|
|
|
|
|
|
|
# Add the rest of the args without specifying a name
|
|
|
|
for extra_arg in args[len(name_and_text_list):]:
|
|
|
|
name_and_text_list.append((None, extra_arg))
|
|
|
|
|
|
|
|
# if no --names are provided, just use the args without a name.
|
|
|
|
else:
|
|
|
|
name_and_text_list = [(None, x) for x in args]
|
|
|
|
|
|
|
|
# Convert the plaintext text objects to bytestrings and collect
|
|
|
|
for name_and_text in name_and_text_list:
|
|
|
|
name, plaintext = name_and_text
|
|
|
|
|
|
|
|
if plaintext == '':
|
|
|
|
raise AnsibleOptionsError('The plaintext provided from the command line args was empty, not encrypting')
|
|
|
|
|
|
|
|
b_plaintext = to_bytes(plaintext)
|
|
|
|
b_plaintext_list.append((b_plaintext, self.FROM_ARGS, name))
|
|
|
|
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
# TODO: specify vault_id per string?
|
2017-02-17 15:12:14 +00:00
|
|
|
# Format the encrypted strings and any corresponding stderr output
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
outputs = self._format_output_vault_strings(b_plaintext_list, vault_id=self.encrypt_vault_id)
|
2017-02-17 15:12:14 +00:00
|
|
|
|
|
|
|
for output in outputs:
|
|
|
|
err = output.get('err', None)
|
|
|
|
out = output.get('out', '')
|
|
|
|
if err:
|
|
|
|
sys.stderr.write(err)
|
|
|
|
print(out)
|
|
|
|
|
|
|
|
if sys.stdout.isatty():
|
|
|
|
display.display("Encryption successful", stderr=True)
|
|
|
|
|
|
|
|
# TODO: offer block or string ala eyaml
|
|
|
|
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
def _format_output_vault_strings(self, b_plaintext_list, vault_id=None):
|
2017-06-12 06:55:19 +00:00
|
|
|
# If we are only showing one item in the output, we don't need to included commented
|
2017-02-17 15:12:14 +00:00
|
|
|
# delimiters in the text
|
|
|
|
show_delimiter = False
|
|
|
|
if len(b_plaintext_list) > 1:
|
|
|
|
show_delimiter = True
|
|
|
|
|
|
|
|
# list of dicts {'out': '', 'err': ''}
|
|
|
|
output = []
|
|
|
|
|
|
|
|
# Encrypt the plaintext, and format it into a yaml block that can be pasted into a playbook.
|
|
|
|
# For more than one input, show some differentiating info in the stderr output so we can tell them
|
|
|
|
# apart. If we have a var name, we include that in the yaml
|
|
|
|
for index, b_plaintext_info in enumerate(b_plaintext_list):
|
|
|
|
# (the text itself, which input it came from, its name)
|
|
|
|
b_plaintext, src, name = b_plaintext_info
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
|
|
|
|
b_ciphertext = self.editor.encrypt_bytes(b_plaintext, self.encrypt_secret,
|
|
|
|
vault_id=vault_id)
|
2017-02-17 15:12:14 +00:00
|
|
|
|
|
|
|
# block formatting
|
|
|
|
yaml_text = self.format_ciphertext_yaml(b_ciphertext, name=name)
|
|
|
|
|
|
|
|
err_msg = None
|
|
|
|
if show_delimiter:
|
|
|
|
human_index = index + 1
|
|
|
|
if name:
|
|
|
|
err_msg = '# The encrypted version of variable ("%s", the string #%d from %s).\n' % (name, human_index, src)
|
|
|
|
else:
|
|
|
|
err_msg = '# The encrypted version of the string #%d from %s.)\n' % (human_index, src)
|
|
|
|
output.append({'out': yaml_text, 'err': err_msg})
|
|
|
|
|
|
|
|
return output
|
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
def execute_decrypt(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' decrypt the supplied file using the provided vault secret '''
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-08-27 07:07:42 +00:00
|
|
|
if len(self.args) == 0 and sys.stdin.isatty():
|
2015-11-10 19:40:55 +00:00
|
|
|
display.display("Reading ciphertext input from stdin", stderr=True)
|
2015-08-27 07:07:42 +00:00
|
|
|
|
2015-08-26 17:21:20 +00:00
|
|
|
for f in self.args or ['-']:
|
|
|
|
self.editor.decrypt_file(f, output_file=self.options.output_file)
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-08-27 07:07:42 +00:00
|
|
|
if sys.stdout.isatty():
|
2015-11-10 19:40:55 +00:00
|
|
|
display.display("Decryption successful", stderr=True)
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-08-26 17:21:20 +00:00
|
|
|
def execute_create(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' create and open a file in an editor that will be encryped with the provided vault secret when closed'''
|
2015-08-26 17:21:20 +00:00
|
|
|
|
|
|
|
if len(self.args) > 1:
|
|
|
|
raise AnsibleOptionsError("ansible-vault create can take only one filename argument")
|
|
|
|
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
self.editor.create_file(self.args[0], self.encrypt_secret,
|
|
|
|
vault_id=self.encrypt_vault_id)
|
2015-08-26 17:21:20 +00:00
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
def execute_edit(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' open and decrypt an existing vaulted file in an editor, that will be encryped again when closed'''
|
2015-04-27 11:31:41 +00:00
|
|
|
for f in self.args:
|
2015-08-26 13:47:37 +00:00
|
|
|
self.editor.edit_file(f)
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
def execute_view(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' open, decrypt and view an existing vaulted file using a pager using the supplied vault secret '''
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
for f in self.args:
|
2016-01-28 18:50:20 +00:00
|
|
|
# Note: vault should return byte strings because it could encrypt
|
|
|
|
# and decrypt binary files. We are responsible for changing it to
|
|
|
|
# unicode here because we are displaying it and therefore can make
|
|
|
|
# the decision that the display doesn't have to be precisely what
|
|
|
|
# the input was (leave that to decrypt instead)
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
plaintext = self.editor.plaintext(f)
|
|
|
|
self.pager(to_text(plaintext))
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-04-27 11:31:41 +00:00
|
|
|
def execute_rekey(self):
|
2017-03-23 05:11:40 +00:00
|
|
|
''' re-encrypt a vaulted file with a new secret, the previous secret is required '''
|
2015-06-21 20:51:07 +00:00
|
|
|
for f in self.args:
|
Support multiple vault passwords (#22756)
Fixes #13243
** Add --vault-id to name/identify multiple vault passwords
Use --vault-id to indicate id and path/type
--vault-id=prompt # prompt for default vault id password
--vault-id=myorg@prompt # prompt for a vault_id named 'myorg'
--vault-id=a_password_file # load ./a_password_file for default id
--vault-id=myorg@a_password_file # load file for 'myorg' vault id
vault_id's are created implicitly for existing --vault-password-file
and --ask-vault-pass options.
Vault ids are just for UX purposes and bookkeeping. Only the vault
payload and the password bytestring is needed to decrypt a
vault blob.
Replace passing password around everywhere with
a VaultSecrets object.
If we specify a vault_id, mention that in password prompts
Specifying multiple -vault-password-files will
now try each until one works
** Rev vault format in a backwards compatible way
The 1.2 vault format adds the vault_id to the header line
of the vault text. This is backwards compatible with older
versions of ansible. Old versions will just ignore it and
treat it as the default (and only) vault id.
Note: only 2.4+ supports multiple vault passwords, so while
earlier ansible versions can read the vault-1.2 format, it
does not make them magically support multiple vault passwords.
use 1.1 format for 'default' vault_id
Vaulted items that need to include a vault_id will be
written in 1.2 format.
If we set a new DEFAULT_VAULT_IDENTITY, then the default will
use version 1.2
vault will only use a vault_id if one is specified. So if none
is specified and C.DEFAULT_VAULT_IDENTITY is 'default'
we use the old format.
** Changes/refactors needed to implement multiple vault passwords
raise exceptions on decrypt fail, check vault id early
split out parsing the vault plaintext envelope (with the
sha/original plaintext) to _split_plaintext_envelope()
some cli fixups for specifying multiple paths in
the unfrack_paths optparse callback
fix py3 dict.keys() 'dict_keys object is not indexable' error
pluralize cli.options.vault_password_file -> vault_password_files
pluralize cli.options.new_vault_password_file -> new_vault_password_files
pluralize cli.options.vault_id -> cli.options.vault_ids
** Add a config option (vault_id_match) to force vault id matching.
With 'vault_id_match=True' and an ansible
vault that provides a vault_id, then decryption will require
that a matching vault_id is required. (via
--vault-id=my_vault_id@password_file, for ex).
In other words, if the config option is true, then only
the vault secrets with matching vault ids are candidates for
decrypting a vault. If option is false (the default), then
all of the provided vault secrets will be selected.
If a user doesn't want all vault secrets to be tried to
decrypt any vault content, they can enable this option.
Note: The vault id used for the match is not encrypted or
cryptographically signed. It is just a label/id/nickname used
for referencing a specific vault secret.
2017-07-28 19:20:58 +00:00
|
|
|
# FIXME: plumb in vault_id, use the default new_vault_secret for now
|
|
|
|
self.editor.rekey_file(f, self.new_encrypt_secret,
|
|
|
|
self.new_encrypt_vault_id)
|
2015-04-20 03:31:44 +00:00
|
|
|
|
2015-11-10 19:40:55 +00:00
|
|
|
display.display("Rekey successful", stderr=True)
|