> In our specific case, the issue is that the client thinks that a given
> CA cert with a name different than "ca" (ie generated by 0.24) is a > regular certificate and not a CA cert. > It may just be me (or lack of coffee) but this sound like the converse of what's described on the ticket (and what we were seeing). I believe 24.8 was creating certs called CA but with the fqdn for the CN; 25.0 wasn't accepting these because it wanted to use "ca" for the CN. -- Markus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
