Project

General

Profile

Actions
Copy link

Bug #14732

closed

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

Added by Nicolas CHARLES over 5 years ago. Updated about 4 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
Techniques
Target version:
4.1.22
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

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 1 (0 open — 1 closed)

Bug #14733: Same as parent ticket for branch 5.0 ReleasedAlexis MoussetActions
Actions
Copy link
 #1

Updated by Nicolas CHARLES over 5 years ago

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

Updated by Nicolas CHARLES over 5 years ago

  • Description updated (diff)
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 5 years 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
Actions
Copy link
 #4

Updated by Rudder Quality Assistant over 5 years ago

  • Assignee changed from Alexis Mousset to Nicolas CHARLES
Actions
Copy link
 #5

Updated by Nicolas CHARLES over 5 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 5 years 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
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 5 years 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.

Actions
Copy link
 #8

Updated by Nicolas Ecarnot about 4 years 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.

Actions
Copy link
 #9

Updated by Nicolas Ecarnot about 4 years 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?

Actions
Copy link
 #10

Updated by Nicolas CHARLES about 4 years 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

Actions
Copy link
 #11

Updated by Nicolas CHARLES about 4 years ago

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

Actions
Copy link
 #12

Updated by Nicolas Ecarnot about 4 years 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 :)

Actions
Copy link

Also available in: Atom PDF