Project

General

Profile

Actions
Copy link

Feature #10115

open

Have the smart proxy report the actual fingerprint of the certificates, not just the hashing algorithm

Added by Xavier L about 9 years ago. Updated over 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Currently the smart-proxy parses and returns only the hashing algorithm of the fingerprint the certificates managed through the puppet CA (source:modules/puppetca/puppetca_main.rb#L151). It should also get the actual fingerprint, as the information is available, and it would allow the fingerprint on the puppet CA to be matched with the fingerprint on the puppet node before signing it (that would require some changes to foreman as well).

I'd be willing to do the patch and submit a pull request.

Actions
Copy link

Also available in: Atom PDF