Issue #1765 has been updated by luke. Status changed from Accepted to Ready for Checkin
Pushed a partial fix to tickets/master/1765. I'm going to open the rest of it as another ticket, since it's dependent on the REST auth file. ---------------------------------------- Bug #1765: Certificate hostnames are not verified http://projects.reductivelabs.com/issues/1765 Author: IanTurner Status: Accepted Priority: Normal Assigned to: Category: SSL Target version: 0.25.0 Complexity: Hard Affected version: 0.24.6 Keywords: certificate security spoof validation authentication dns The puppetmaster only verifies the validity of the client certificate, but does not verify the associated hostname. Thus a client with a certificate signed as "publicserver" can instead claim to be "secretserver" and gain access to the latter's configuration. This certificate hostname spoofing can be a serious issue, since client configuration may include password hashes and other confidential data. The best approach to client validation is to verify that all three of the following are identical at the FQDN level: 1. The FQDN on the signed client certificate. 2. The FQDN presented by the client facter invocation. 3. The result of a reverse lookup on the connecting client IP address. Additionally, an address (A/AAAA record, not CNAME record) lookup on this FQDN should in turn yield the connecting client IP address in the query result. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
