usermod, newusers, prefix: enforce absolute paths for homedir#352
Conversation
useradd already was enforcing this, but these were not. Signed-off-by: Serge Hallyn <serge@hallyn.com>
|
With this change it is not possible anymore to unset the user home directory. What is the suggested workaround or is this a regression? |
So if user w3m has homedir /home/w3m you want to usermod -d "" ? I guess the suggested workaround would be to just use a nonexistent path, but yes this is a regression. Would you mind opening an issue for it (assigned to me), or if you prefer posting a patch to fix it (by just adding a check for it being the empty string and allowing that). |
Related to: shadow-maint#352 Signed-off-by: Volker Theile <votdev@gmx.de>
With the PR 352 it is not possible anymore to run `usermod --home "" <USERNAME>`. This PR will fix that regression. Related to: shadow-maint#352 Signed-off-by: Volker Theile <votdev@gmx.de>
If opened the PR #1133. |
With the PR 352 it is not possible anymore to run `usermod --home "" <USERNAME>`. This PR will fix that regression. Related to: shadow-maint#352 Signed-off-by: Volker Theile <votdev@gmx.de>
With the PR 352 it is not possible anymore to run `usermod --home "" <USERNAME>`. This PR will fix that regression. Related to: shadow-maint#352 Signed-off-by: Volker Theile <votdev@gmx.de>
With the PR 352 it is not possible anymore to run `usermod --home "" <USERNAME>`. This PR will fix that regression. Related to: #352 Signed-off-by: Volker Theile <votdev@gmx.de>
2 participants
useradd already was enforcing this, but these were not.
Signed-off-by: Serge Hallyn serge@hallyn.com