Project

General

Profile

Bug #14732

Technique "SSH authorized keys" creates home directory with perms root:root when it does not exists yet

Added by Nicolas CHARLES over 1 year ago. Updated 16 days ago.

Status:
Released
Priority:
N/A
Category:
Techniques
Target version:
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Effort required:
Priority:
0

Description

When using sshKeyDistribution with a home directory not set (but user existing), it create home directory with perms 700:root:root, but.ssh and authorized_keys have correct permissions

It should create the home with correct permissions


Subtasks

Bug #14733: Same as parent ticket for branch 5.0 ReleasedAlexis MOUSSETActions
#1

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from New to In progress
  • Assignee set to Nicolas CHARLES
#2

Updated by Nicolas CHARLES over 1 year ago

  • Description updated (diff)
#3

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Nicolas CHARLES to Alexis MOUSSET
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1430
#4

Updated by Rudder Quality Assistant over 1 year ago

  • Assignee changed from Alexis MOUSSET to Nicolas CHARLES
#5

Updated by Nicolas CHARLES over 1 year ago

  • Status changed from Pending technical review to Pending release
#6

Updated by Vincent MEMBRÉ over 1 year ago

  • Subject changed from sshKeyDistribution creates home directory with perms root:root when it does not exists yet to Technique "SSH authorized keys" creates home directory with perms root:root when it does not exists yet
#7

Updated by Vincent MEMBRÉ over 1 year ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.22, 4.3.12 and 5.0.10 which were released today.

#8

Updated by Nicolas Ecarnot 29 days ago

Hello,

I'm just realizing I'm facing this same bug with :
  1. rudder agent version
    Rudder agent 6.1.6.release

I removed /home/my_user, then ran rudder agent run -u, and the /home/my_user directory, as well as the underlying .ssh directory was owned by root:root
The authorized_keys owner and group are correct though.

#9

Updated by Nicolas Ecarnot 16 days ago

  • Severity set to Major - prevents use of part of Rudder | no simple workaround

Hello,

This bug prevents the success of next steps in the setup of an account, so could one re-open this issue please?

#10

Updated by Nicolas CHARLES 16 days ago

Hi Nicolas. Which version of the technique are you using ?
Also, techniques used to not be automatically updated at Rudder upgrade. Is it a fresh install, or an upgrade from a Rudder before 6.0 ? Is the later, you'll need to run

rudder server upgrade-techniques -o

to force upgrading your techniques

#11

Updated by Nicolas CHARLES 16 days ago

If you are using technique version 4.0, it should have been fixed in https://issues.rudder.io/issues/14733

#12

Updated by Nicolas Ecarnot 16 days ago

Nicolas CHARLES wrote in #note-11:

If you are using technique version 4.0, it should have been fixed in https://issues.rudder.io/issues/14733

Yes sir, I second that :)

Also available in: Atom PDF