On 28/12/09 22:55, Peter Meier wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> cool! thanks!
>
>> This patch adds two things:
>>   * certificate fingerprinting in --list mode
>>   * a puppetca action called "--fingerprint" to display fingerprints
>> of given certificates
>>
>> It is also possible to use --digest to specify a specific digest
>> algorithm.
>
> and how is the fingerprint print on the client? I don't really see that
> in your code.

Hmm, I guess I didn't fully read the ticket :-(

I just thought it was for fingerprinting signed certificates whereas you 
want to fingerprint certificate signing requests which is a different 
story...

I'm able to easily fingerprint the csr on the master, but as you say in 
the ticket we don't have a puppetca for the client. I'm wondering if we 
couldn't print the fingerprint when it is generated by the client.
This way it would at least appear in the logs.

Of course we can add a puppetd option as you suggest... I'm just trying 
to find something lightweight...

So comments/ideas are welcome :-)
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

--

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.


Reply via email to