summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSilvio Rhatto <rhatto@riseup.net>2010-06-13 13:40:42 -0300
committerSilvio Rhatto <rhatto@riseup.net>2010-06-13 13:40:42 -0300
commit392a325337c18e752c9ec32b583520f404225538 (patch)
tree8a58f347d8221b7fb88d8bbe1325992b7f386f49
parent95888958b1ca4fa6e9045da3050cd64403f938c7 (diff)
downloadpadrao-392a325337c18e752c9ec32b583520f404225538.tar.gz
padrao-392a325337c18e752c9ec32b583520f404225538.tar.bz2
Verificacoes adicionais de certificados no puppet
-rw-r--r--puppet.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/puppet.mdwn b/puppet.mdwn
index 9ee2c9f..65ec4a3 100644
--- a/puppet.mdwn
+++ b/puppet.mdwn
@@ -204,10 +204,12 @@ Caso contrário, simplesmente inicie-o com
Em seguida, verifique se os fingerprints dos certificados (master e nodo) coincidem. No master (use `/var/lib/puppet` caso esta seja a pasta utilizada pelo master):
openssl x509 -text -noout -fingerprint -in /var/lib/puppetmaster/ssl/ca/requests/camada.projeto.org.pem
+ openssl x509 -text -noout -fingerprint -in /var/lib/puppetmaster/ssl/certs/ca.pem
No nodo:
openssl x509 -text -noout -fingerprint -in /var/lib/puppet/ssl/certs/camada.projeto.org.pem
+ openssl x509 -text -noout -fingerprint -in /var/lib/puppet/ssl/certs/ca.pem
Caso os fingerprints batam, basta liberar o novo nodo a partir do host em que roda o master como o comando