Security and certificates
- Spring4Shell statement
- Puppet response to recent Log4j vulnerabilities FAQ
- Fix an “ERROR: You’re using an RSA key with SHA-1” error message in Puppet Enterprise
- Troubleshooting LDAP integration issues in Puppet Enterprise
- Fix a “Could not run: The certificate” error message on an agent node in Puppet Enterprise
- Get the Puppet CA certificate chain in Puppet Enterprise
- “Access denied” errors on Windows nodes after adding a Group Policy to the Application event log in Puppet Enterprise
- Regenerating a primary server certificate in Puppet Enterprise fails
- Resolve an expired certificate revocation list error message on an agent node in Puppet Enterprise
- Troubleshoot a “returned 60: curl: (60) SSL certificate problem: self signed certificate” error in Puppet Comply
- Get a list of DNS alt names from a compiler certificate in Puppet Enterprise
- Puppet response to the recent Java vulnerability
- Recommended reading: Find and mitigate Log4j vulnerabilities with Puppet Enterprise
- Certificate validation error when updating an expired GPG key in Puppet Enterprise 2016.4.0 to 2019.8.4
- How certificates work in Puppet
- A security scanner flagged Puppet Enterprise ports as vulnerable because of a lack of HSTS headers
- Tasks and plans shipped in Puppet Enterprise
- Tech Talk: Configuring Puppet's policy-based autosigning
- "nested asn1 error" when running “puppet cert clean” in Puppet Enterprise 2019.1 and later
- Check and fix the expiry date for your CA certificate in Puppet Enterprise
- Set SSL cipher suites in Puppet Enterprise 2018.1 and later
- Errors authenticating with your LDAP user account in the Puppet Enterprise console after generating a new self-signed certificate for your directory server
- Add custom HTTP headers to NGINX in Puppet Enterprise 2016.4, 2017.3, 2018.1, 2019.2
- Regenerate the primary server certificate in Puppet Enterprise 2018.1.8 and later
- Add certificates to the Puppet certificate bundle in Puppet Enterprise
- Resolve a duplicate declaration error when adding a hostname to the certificate authority whitelist in the console for Puppet Enterprise 2016.2 to 2019.2.2 and 2019.5
- Use the API to sign certificate signing requests from non-certificate authority nodes for Puppet Enterprise
- Obfuscate hostnames and IP addresses in support script output using SOScleaner
- Verify SSL protocols and cipher suites in use on Puppet Enterprise nodes
- Resolve a "header too long" error when using "puppet cert" or "puppet node" commands in Puppet Enterprise 3.2 to 2016.2 and 2017.1 to 2018.1