Security and certificates
- 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 2018.1 and later
- 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
- CVE-2017-15059 in Puppet Enterprise 2016.4.0 to 2016.4.9, 2017.2.x, 2017.3.0 to 2017.3.2
- Unsigned Certificates page unavailable and cert "Error: header too long errors" in Puppet Enterprise 2016.4.7
- Add certificates to the Puppet certificate bundle in Puppet Enterprise 2015.2 to 2019.0
- Recommended reading - Detecting and remediating WannaCry for Puppet Enterprise 2015.2 to 2017.2
- 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 2016.2 to 2017.1, 2017.3 to 2019.2
- Obfuscate hostnames and IP addresses in support script output using SOScleaner
- Renew expiring certificates for Puppet Enterprise 3.7 to 2017.3
- Verify SSL protocols and cipher suites in use on Puppet Enterprise nodes
- Workaround for October 2016 remote code execution CVE for Puppet Enterprise 2016.2.x, 2016.1.x, and 2015.3.x
- "nested asn1 error" when running “puppet cert clean” in Puppet Enterprise 2016.2.1
- Change the SSL protocol of the console service for Puppet Enterprise 2015.2 to 2016.4.3
- 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
- Install PE-only modules without internet access for Puppet Enterprise 2016.2 to 2017.2
- Resolve agent certificates that use the hostname instead of the FQDN as the cert name for Puppet Enterprise 3.3 to 3.8 or 2015.2 to 2015.3
- Enable protocol security in Razor with a custom certificate authority in Puppet Enterprise
- How do I encrypt files that I'm sending to Support?
- Install PE-only modules without internet access for Puppet Enterprise 2015.2.x to 2016.1.x
- Learn more about security and bug fixes for Puppet products
- Regenerate a compile master certificate in Puppet Enterprise 2015.2.x