Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
-
Froyo
-
1
-
Major
-
3 - 25-50% of Customers
-
4 - Major
-
4 - $$$$$
-
Faced by anyone with large scale decommissioning of nodes.
Description
The CRL file (and many other SSL related files) are missing locking, so concurrent access can lead to corruptions.
In Scope
Confirm that PE in the Cloud etc will be leveraging puppet cert command line tools (as opposed to modifying CRL directly or revoking certs via server http api)confirmed- Investigate filesystem-based locking of CRL file in ruby puppet on update
- Limited to updates to CRL via the puppet cert CLI
Out of Scope
- Changes to puppet server CRL handling / API -
PUP-7991
Attachments
Issue Links
- is duplicated by
-
PUP-3703 puppca appears to have a race condition on the ca_crl.pem creation with many parallel revocations
-
- Closed
-
- relates to
-
SERVER-115 Concurrent access to the CRL can corrupt it
-
- Resolved
-
-
PUP-1627 Puppet agent's locking is subject to race conditions
-
- Closed
-
-
SERVER-1999 Investigate puppet server CRL handling for atomicity
-
- Closed
-
(3 mentioned in)