Actions
Bug #6412
closed
Technique uses /root as an hardcoded value for the home of user root
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
60
Name check:
Fix check:
Regression:
Description
System technique uses an hardcoded /root reference for managing postgresql password.
However, /root may not be the home of root (sometimes it is /home/root for instance); and when it is not /root the agent fails completly on the rudder server - it tries to ask password to access the database, but there is noone to answer.
Updated by Jonathan CLARKE about 8 years ago
- Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
- User visibility set to Infrequent - complex configurations | third party integrations
Updated by
Updated by Vincent MEMBRÉ about 7 years ago
- Target version changed from 4.1.11 to 4.1.12
- Priority changed from 54 to 55
Updated by Vincent MEMBRÉ almost 7 years ago
- Target version changed from 4.1.13 to 4.1.14
- Priority changed from 55 to 56
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.15 to 4.1.16
- Priority changed from 56 to 57
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.16 to 4.1.17
- Priority changed from 57 to 58
Updated by Vincent MEMBRÉ over 6 years ago
- Target version changed from 4.1.18 to 4.1.19
- Priority changed from 58 to 59
Updated by
Updated by Nicolas CHARLES over 6 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/1412
Updated by Nicolas CHARLES over 6 years ago
- Status changed from Pending technical review to Pending release
Updated by François ARMAND over 6 years ago
- Status changed from Pending release to Released
- Priority changed from 59 to 60
Actions