Puppet-Passwords as plain text in Windows agent output and in catalog file
up vote
0
down vote
favorite
I encrypted password using hiera:
dsc_xADUser {'FirstUser':
dsc_ensure => 'present',
dsc_domainname => 'ad.contoso.com',
dsc_username => 'tfl',
dsc_userprincipalname => 'tfl@ad.contoso.com',
dsc_password => {
'user' => 'tfl@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
dsc_passwordneverexpires => true,
dsc_domainadministratorcredential => {
'user' => 'Administrator@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
}
but on node,when running agent -t -v
password is shown as plain text in agent output and in catalog JSON file.
I also tried node_encrypt(lookup('password')) then getting content of my encrypted password (which is good) and windows complains that password doesn't meet password complexity (bad-because it's trying to set all below as password)
'password' = '-----BEGIN PKCS7-----
MIIMyQYJKoZIhvcNAQcDoIIMujCCDLYCAQAxggKdMIICmQIBADCBgjB9MXsweQYD
VQQDDHJQdXBwZXQgRW50ZXJwcmlzZSBDQSBnZW5lcmF0ZWQgb24gbXlwdXBwZXQt
eGwwZGJ5a212Z2xrYnl2eS5ldS13ZXN0LTEub3Bzd29ya3MtY20uaW8gYXQgKzIw
MTgtMTEtMDIgMTQ6MDQ6MDAgKzAwMDACAQUwCwYJKoZIhvcNAQEBBIICABkJDfGb
4CdHUntrVR1E......
hiera config:
---
version: 5
defaults:
datadir: data
data_hash: yaml_data
hierarchy:
- name: "Eyaml hierarchy"
lookup_key: eyaml_lookup_key # eyaml backend
paths:
- "nodes/%{trusted.certname}.yaml"
- "windowspass.eyaml"
options:
pkcs7_private_key: "/etc/puppetlabs/puppet/keys/private_key.pkcs7.pem"
pkcs7_public_key: "/etc/puppetlabs/puppet/keys/public_key.pkcs7.pem"
EDIT: just found this, it seems it's opened issue and related to Windows only
UPDATE: i managed to configure puppet not to cache catalog file on Windows client (adding catalog_cache_terminus=""
to puppet config file on windows so i'll use this as "workaround", it seems no way to remove passwords from agent debug output
puppet puppet-enterprise hiera
add a comment |
up vote
0
down vote
favorite
I encrypted password using hiera:
dsc_xADUser {'FirstUser':
dsc_ensure => 'present',
dsc_domainname => 'ad.contoso.com',
dsc_username => 'tfl',
dsc_userprincipalname => 'tfl@ad.contoso.com',
dsc_password => {
'user' => 'tfl@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
dsc_passwordneverexpires => true,
dsc_domainadministratorcredential => {
'user' => 'Administrator@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
}
but on node,when running agent -t -v
password is shown as plain text in agent output and in catalog JSON file.
I also tried node_encrypt(lookup('password')) then getting content of my encrypted password (which is good) and windows complains that password doesn't meet password complexity (bad-because it's trying to set all below as password)
'password' = '-----BEGIN PKCS7-----
MIIMyQYJKoZIhvcNAQcDoIIMujCCDLYCAQAxggKdMIICmQIBADCBgjB9MXsweQYD
VQQDDHJQdXBwZXQgRW50ZXJwcmlzZSBDQSBnZW5lcmF0ZWQgb24gbXlwdXBwZXQt
eGwwZGJ5a212Z2xrYnl2eS5ldS13ZXN0LTEub3Bzd29ya3MtY20uaW8gYXQgKzIw
MTgtMTEtMDIgMTQ6MDQ6MDAgKzAwMDACAQUwCwYJKoZIhvcNAQEBBIICABkJDfGb
4CdHUntrVR1E......
hiera config:
---
version: 5
defaults:
datadir: data
data_hash: yaml_data
hierarchy:
- name: "Eyaml hierarchy"
lookup_key: eyaml_lookup_key # eyaml backend
paths:
- "nodes/%{trusted.certname}.yaml"
- "windowspass.eyaml"
options:
pkcs7_private_key: "/etc/puppetlabs/puppet/keys/private_key.pkcs7.pem"
pkcs7_public_key: "/etc/puppetlabs/puppet/keys/public_key.pkcs7.pem"
EDIT: just found this, it seems it's opened issue and related to Windows only
UPDATE: i managed to configure puppet not to cache catalog file on Windows client (adding catalog_cache_terminus=""
to puppet config file on windows so i'll use this as "workaround", it seems no way to remove passwords from agent debug output
puppet puppet-enterprise hiera
Thedsc_xADUser
provider(s) may not fully support theSensitive
data type with regard to logging. You should probably open an issue for the module about this.
– Matt Schuchard
Nov 5 at 15:42
have no credentials to their JIRA :)
– xerks
Nov 5 at 15:51
It is a puppetlabs module? You can create an account in their JIRA for free to post it. If you have a Puppet Enterprise support account, you can open a ticket pointing at the issue to expedite it.
– Matt Schuchard
Nov 5 at 15:53
yes, it's puppetlab module, just created issue, thanks:tickets.puppetlabs.com/browse/MODULES-8213
– xerks
Nov 5 at 16:12
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I encrypted password using hiera:
dsc_xADUser {'FirstUser':
dsc_ensure => 'present',
dsc_domainname => 'ad.contoso.com',
dsc_username => 'tfl',
dsc_userprincipalname => 'tfl@ad.contoso.com',
dsc_password => {
'user' => 'tfl@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
dsc_passwordneverexpires => true,
dsc_domainadministratorcredential => {
'user' => 'Administrator@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
}
but on node,when running agent -t -v
password is shown as plain text in agent output and in catalog JSON file.
I also tried node_encrypt(lookup('password')) then getting content of my encrypted password (which is good) and windows complains that password doesn't meet password complexity (bad-because it's trying to set all below as password)
'password' = '-----BEGIN PKCS7-----
MIIMyQYJKoZIhvcNAQcDoIIMujCCDLYCAQAxggKdMIICmQIBADCBgjB9MXsweQYD
VQQDDHJQdXBwZXQgRW50ZXJwcmlzZSBDQSBnZW5lcmF0ZWQgb24gbXlwdXBwZXQt
eGwwZGJ5a212Z2xrYnl2eS5ldS13ZXN0LTEub3Bzd29ya3MtY20uaW8gYXQgKzIw
MTgtMTEtMDIgMTQ6MDQ6MDAgKzAwMDACAQUwCwYJKoZIhvcNAQEBBIICABkJDfGb
4CdHUntrVR1E......
hiera config:
---
version: 5
defaults:
datadir: data
data_hash: yaml_data
hierarchy:
- name: "Eyaml hierarchy"
lookup_key: eyaml_lookup_key # eyaml backend
paths:
- "nodes/%{trusted.certname}.yaml"
- "windowspass.eyaml"
options:
pkcs7_private_key: "/etc/puppetlabs/puppet/keys/private_key.pkcs7.pem"
pkcs7_public_key: "/etc/puppetlabs/puppet/keys/public_key.pkcs7.pem"
EDIT: just found this, it seems it's opened issue and related to Windows only
UPDATE: i managed to configure puppet not to cache catalog file on Windows client (adding catalog_cache_terminus=""
to puppet config file on windows so i'll use this as "workaround", it seems no way to remove passwords from agent debug output
puppet puppet-enterprise hiera
I encrypted password using hiera:
dsc_xADUser {'FirstUser':
dsc_ensure => 'present',
dsc_domainname => 'ad.contoso.com',
dsc_username => 'tfl',
dsc_userprincipalname => 'tfl@ad.contoso.com',
dsc_password => {
'user' => 'tfl@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
dsc_passwordneverexpires => true,
dsc_domainadministratorcredential => {
'user' => 'Administrator@ad.contoso.com',
'password' => Sensitive(lookup('password'))
},
}
but on node,when running agent -t -v
password is shown as plain text in agent output and in catalog JSON file.
I also tried node_encrypt(lookup('password')) then getting content of my encrypted password (which is good) and windows complains that password doesn't meet password complexity (bad-because it's trying to set all below as password)
'password' = '-----BEGIN PKCS7-----
MIIMyQYJKoZIhvcNAQcDoIIMujCCDLYCAQAxggKdMIICmQIBADCBgjB9MXsweQYD
VQQDDHJQdXBwZXQgRW50ZXJwcmlzZSBDQSBnZW5lcmF0ZWQgb24gbXlwdXBwZXQt
eGwwZGJ5a212Z2xrYnl2eS5ldS13ZXN0LTEub3Bzd29ya3MtY20uaW8gYXQgKzIw
MTgtMTEtMDIgMTQ6MDQ6MDAgKzAwMDACAQUwCwYJKoZIhvcNAQEBBIICABkJDfGb
4CdHUntrVR1E......
hiera config:
---
version: 5
defaults:
datadir: data
data_hash: yaml_data
hierarchy:
- name: "Eyaml hierarchy"
lookup_key: eyaml_lookup_key # eyaml backend
paths:
- "nodes/%{trusted.certname}.yaml"
- "windowspass.eyaml"
options:
pkcs7_private_key: "/etc/puppetlabs/puppet/keys/private_key.pkcs7.pem"
pkcs7_public_key: "/etc/puppetlabs/puppet/keys/public_key.pkcs7.pem"
EDIT: just found this, it seems it's opened issue and related to Windows only
UPDATE: i managed to configure puppet not to cache catalog file on Windows client (adding catalog_cache_terminus=""
to puppet config file on windows so i'll use this as "workaround", it seems no way to remove passwords from agent debug output
puppet puppet-enterprise hiera
puppet puppet-enterprise hiera
edited Nov 9 at 17:05
asked Nov 5 at 11:54
xerks
7311
7311
Thedsc_xADUser
provider(s) may not fully support theSensitive
data type with regard to logging. You should probably open an issue for the module about this.
– Matt Schuchard
Nov 5 at 15:42
have no credentials to their JIRA :)
– xerks
Nov 5 at 15:51
It is a puppetlabs module? You can create an account in their JIRA for free to post it. If you have a Puppet Enterprise support account, you can open a ticket pointing at the issue to expedite it.
– Matt Schuchard
Nov 5 at 15:53
yes, it's puppetlab module, just created issue, thanks:tickets.puppetlabs.com/browse/MODULES-8213
– xerks
Nov 5 at 16:12
add a comment |
Thedsc_xADUser
provider(s) may not fully support theSensitive
data type with regard to logging. You should probably open an issue for the module about this.
– Matt Schuchard
Nov 5 at 15:42
have no credentials to their JIRA :)
– xerks
Nov 5 at 15:51
It is a puppetlabs module? You can create an account in their JIRA for free to post it. If you have a Puppet Enterprise support account, you can open a ticket pointing at the issue to expedite it.
– Matt Schuchard
Nov 5 at 15:53
yes, it's puppetlab module, just created issue, thanks:tickets.puppetlabs.com/browse/MODULES-8213
– xerks
Nov 5 at 16:12
The
dsc_xADUser
provider(s) may not fully support the Sensitive
data type with regard to logging. You should probably open an issue for the module about this.– Matt Schuchard
Nov 5 at 15:42
The
dsc_xADUser
provider(s) may not fully support the Sensitive
data type with regard to logging. You should probably open an issue for the module about this.– Matt Schuchard
Nov 5 at 15:42
have no credentials to their JIRA :)
– xerks
Nov 5 at 15:51
have no credentials to their JIRA :)
– xerks
Nov 5 at 15:51
It is a puppetlabs module? You can create an account in their JIRA for free to post it. If you have a Puppet Enterprise support account, you can open a ticket pointing at the issue to expedite it.
– Matt Schuchard
Nov 5 at 15:53
It is a puppetlabs module? You can create an account in their JIRA for free to post it. If you have a Puppet Enterprise support account, you can open a ticket pointing at the issue to expedite it.
– Matt Schuchard
Nov 5 at 15:53
yes, it's puppetlab module, just created issue, thanks:tickets.puppetlabs.com/browse/MODULES-8213
– xerks
Nov 5 at 16:12
yes, it's puppetlab module, just created issue, thanks:tickets.puppetlabs.com/browse/MODULES-8213
– xerks
Nov 5 at 16:12
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53153923%2fpuppet-passwords-as-plain-text-in-windows-agent-output-and-in-catalog-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The
dsc_xADUser
provider(s) may not fully support theSensitive
data type with regard to logging. You should probably open an issue for the module about this.– Matt Schuchard
Nov 5 at 15:42
have no credentials to their JIRA :)
– xerks
Nov 5 at 15:51
It is a puppetlabs module? You can create an account in their JIRA for free to post it. If you have a Puppet Enterprise support account, you can open a ticket pointing at the issue to expedite it.
– Matt Schuchard
Nov 5 at 15:53
yes, it's puppetlab module, just created issue, thanks:tickets.puppetlabs.com/browse/MODULES-8213
– xerks
Nov 5 at 16:12