Project

General

Profile

Bug #10852

Node key display differences

Added by Florian Heigl 6 months ago. Updated 2 months ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
48

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.

Associated revisions

Revision e6a537a3
Added by Raphaël Gauthier 3 months ago

Fixes #10852: Node key display differences

History

#1 Updated by François ARMAND 5 months ago

  • 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).

#2 Updated by François ARMAND 5 months ago

  • Priority changed from 0 to 35

#3 Updated by François ARMAND 5 months ago

  • 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

#4 Updated by François ARMAND 5 months ago

  • Assignee set to Raphael GAUTHIER

#5 Updated by Vincent MEMBRÉ 5 months ago

  • Target version changed from 4.0.7 to 357

#6 Updated by Benoît PECCATTE 5 months ago

  • Priority changed from 35 to 49

#7 Updated by Alexis MOUSSET 5 months ago

  • Target version changed from 357 to 4.1.6

#8 Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 4.1.6 to 4.1.7
  • Priority changed from 49 to 48

#9 Updated by Raphael GAUTHIER 3 months ago

  • Status changed from New to In progress

#10 Updated by Raphael GAUTHIER 3 months ago

  • 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

#11 Updated by Anonymous 3 months ago

  • Status changed from Pending technical review to Pending release

#12 Updated by Vincent MEMBRÉ 2 months ago

  • 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