summaryrefslogtreecommitdiffstats
path: root/spec/integration/ssl
Commit message (Collapse)AuthorAgeFilesLines
* Fix #2082 - puppetca shouldn't list revoked certificatesBrice Figureau2009-07-071-5/+3
| | | | | | | | This patch does two things: * it enhance puppetca to list revoked certificates (prefixed by -) * it fixes the ca crl verification which was broken Signed-off-by: Brice Figureau <brice-puppet@daysofwonder.com>
* Fix #2113 - Make temp directoryPaul Nasrat2009-04-051-0/+2
| | | | | Tests were failing this patch makes the temporary directory in line with other integration tests.
* Changing the Cacher.invalidate method to Cacher.expire.Luke Kanies2008-11-114-4/+4
| | | | Signed-off-by: Luke Kanies <luke@madstop.com>
* Using the new Cacher class for handling cached data.Luke Kanies2008-05-134-17/+4
| | | | | This provides a single, global bit for determining whether a given piece of cached data is still valid.
* The CRL is now automatically used or ignored.Luke Kanies2008-05-071-8/+1
| | | | | | | | | Previously, you had to configure whether you wanted the CRL or not, which resulted in errors all the time when it was configured but unavailable. Now, Puppet will always create and try to use it, but you won't get failures if it's unavailable.
* The master and client now successfully speak xmlrpc using the new system.Luke Kanies2008-05-071-0/+2
| | | | | | The server is actually serving REST, but the client can't use it until we resolve the format and security issues that REST hasn't yet tackled.
* Fixing the HttpPool module to get rid of an infinite loop.Luke Kanies2008-05-062-3/+20
| | | | | | | | | We can't have the HttpPool class use the Indirector to see if it has a cert available, because it might be being used to try to download one, which would cause it to make an http instance, which would cause it to... Well, you get the idea. Adding and fixing a few other tests I ran into on the way.
* The Certificate Authority now automatically creates a CRL when appropriate.Luke Kanies2008-05-051-1/+11
| | | | This requires less setup and configuration on the part of the user.
* Fixing a critical problem in how CRLs were saved and moving SSL Store ↵Luke Kanies2008-05-051-0/+45
| | | | | | | | | | | | | | responsibilities to the SSL::Host class. I was previously saving invalid CRLs unless they'd had a revocation done in them; this commit fixes them so that they're always valid. Also, I've added to SSL::Host the ability to generate a valid SSL Store, suitable for validation. This is now used by Webrick and can be used by the http clients, too. This should have been two commits, but I'm kind of down the rabbit hole ATM.
* The CA now initializes itself.Luke Kanies2008-05-051-0/+2
| | | | | | | I realized that it never made sense to have a CA that didn't know how to initialize itself, so we now have a singleton method for the CA, and it also automatically initializes itself.
* I think I've now got the Webrick SSL support working.Luke Kanies2008-04-281-1/+12
| | | | | Now I just need to get xmlrpc working alongside REST in both mongrel and webrick.
* Temporarily disabling the revoke/verify test in the CA.Luke Kanies2008-04-191-3/+5
| | | | | It looks like it's not taking the CRL into account, so I can't seem to actually get a cert to fail verification.
* Finishing the interface between the CA and the CRL.Luke Kanies2008-04-191-1/+15
| | | | | | Certificate revocation now works, the CA knows how to generate the CRL, and the SSL::Host class knows how to configure the CRL class for indirection.
* All SSL terminus classes now force the CA information into the right place.Luke Kanies2008-04-181-0/+10
| | | | | | | | | Without this, then you could end up duplicating your CA key into the normal directory depending on how caching was set up. Again, this design aspect isn't the most straightforward, but at least it's functional now.
* Switching the SSL::Host class to return Puppet instances.Luke Kanies2008-04-171-1/+1
| | | | | | | | | Previously, the class was returning OpenSSL instances (e.g, OpenSSL::X509::Certificate) instead of Puppet instances (e.g., Puppet::SSL::Certificate). This made some things easier, but it made them asymmetric (e.g., you assigned the key as a Puppet instance but got back an OpenSSL instance), and it also reduced your flexibility and introspectiveness.
* Adding integration tests for a lot of the SSL code.Luke Kanies2008-04-173-0/+233
This flushed out some problems, and things mostly look good now, but I don't think we're quite there yet.