Bug #10852
closed
Node key display differences
Added by Florian Heigl over 7 years ago.
Updated about 7 years ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Description
Hi,
in "rudder agent info" we're shown the key hash as per cf-keys.
In the web interface we instead see the key as per the ppkeys/localhost.pub file.
Those infos cannot be compared and rudder should display the same thing in both places.
- Target version set to 3.1.21
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Technique editor | Rudder settings
- Effort required set to Very Small
So, the best solution would be to also display the cfkey hash in the webapp.
It is given in 4.1, and harder in 3.1 (because in 4.1, we already have everything needed to calculate the CFEngine key hash, and it would be quite some code/dependencies to backport to 3.1 - but it must be checked).
- Priority changed from 0 to 35
- Target version changed from 3.1.21 to 4.0.7
So, it is doable in 4.0 and 4.1 trivially: just display the NodeInfo.cfengineKeyHash property in the UI, in node details "Display Node key" and updating the text to:
Display Node key:
Public Key:
-----BEGIN RSA PUBLIC KEY-----
.....
-----END RSA PUBLIC KEY-----
CFEngine Key Hash:
here-the-result-of-NodeInfo.cfengineKeyHash
- Assignee set to Raphael GAUTHIER
- Target version changed from 4.0.7 to 357
- Priority changed from 35 to 49
- Target version changed from 357 to 4.1.6
- Target version changed from 4.1.6 to 4.1.7
- Priority changed from 49 to 48
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1725
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.7 and 4.2.0~rc1 which were released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by Anonymous