Project

General

Profile

Actions

Bug #5930

closed

sshKeyDistribution creates 0 byte authorized_keys file

Added by Florian Heigl over 9 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Techniques
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Hi,

I'm only getting a 0 byte .ssh/authorized_keys for the users.
My suspicion is this is only happening since I added a second technique for user creation.

I can produce it on two different envs, running different versions.

Attaching the file sshKeyDistribution.cf from test client.
rudderc1:/var/rudder/cfengine-community/inputs/sshKeyDistribution/3.0

This one box is actually running a dated client
rudder-agent-2.11.3.release-1.SLES.11

But the other lab is on a more recent one, so I don't think there is a relation to the agent.

I checked, my technique on the server is == the one in git.

[FAR] workaround:

For people relying on that technique and not wanting to wait for a new release: the culprit is "ifvarclass => "key_parsed"" in sshKeyDistribution.st, and removing it fixes the issue.
See: https://github.com/ncharles/rudder-techniques/commit/ef19e241bc3de426a1ac0064b0d767057b8889b3


Files

k.txt (9.55 KB) k.txt Florian Heigl, 2014-12-05 12:35

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #5561: "sshKeyDistribution" Technique keeps adding the same keys for everReleasedJonathan CLARKE2014-09-20Actions
Actions

Also available in: Atom PDF