Actions
Bug #26432
closedWhen using an external database, special characters are breaking the password detection
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
A user reported that the file /opt/rudder/etc/external-db.conf is not correctly read and the password is not corectly configured when using special charaters (at least $ )
Updated by Vincent MEMBRÉ 4 months ago
- Target version changed from 8.2.5 to 8.2.6
Updated by François ARMAND 4 months ago
- Assignee set to Benoît PECCATTE
- Priority changed from To review to 2
So, the source file /opt/rudder/etc/external-db.conf
is dotsourced, then a sed is done, so it's likely why some chars are not correctly escaped.
We should:
- as a workaround, document the accepted chars (but there's no obvious reason to force restraining the char scope, esp if the pass is generated by some cloud provider)
- correctly escape the pass before copying it.
Updated by Vincent MEMBRÉ about 2 months ago
- Target version changed from 8.2.6 to 8.2.7
Updated by Benoît PECCATTE 29 days ago
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2992
Updated by Benoît PECCATTE 26 days ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|05d2abee74998e2258ebe29adb6a3fb9c9f9a6cc.
Updated by Vincent MEMBRÉ 16 days ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.2.7 and 8.3.2 which were released today.
Actions