HomePhorge

Fixing #2028 - Better failures when a cert is found with no key
09bee9137d7aUnpublished

Unpublished Commit ยท Learn More

Repository Importing: This repository is still importing.

Description

Fixing #2028 - Better failures when a cert is found with no key

The problem was that the server had a certificate
for the client. Initially the client just didn't have a
key, because it assumed that if it had a certificate then
it had a key. Upon fixing it to create the key, the key then
did not match the found certificate.

This commit fixes both of those: The key is always found
before the certificate, and when the certificate is found
it's verified against the private key and an exception
is thrown if they don't match.

It's always a failure, so this just makes the failure
more informative.

Signed-off-by: Luke Kanies <luke@madstop.com>

Details

Provenance
Luke Kanies <luke@madstop.com>Authored on
James Turnbull <james@lovedthanlost.net>Committed on Feb 28 2009, 1:09 AM
vanmeeuwenPushed on Jun 2 2015, 2:22 PM
Parents
rPUcf1cb1474f13: Moving the clientyamldir setting into the puppetd section
Branches
Unknown
Tags
Unknown

Event Timeline

James Turnbull <james@lovedthanlost.net> committed rPU09bee9137d7a: Fixing #2028 - Better failures when a cert is found with no key (authored by Luke Kanies <luke@madstop.com>).Feb 28 2009, 1:09 AM