[Possible bug] Changing SSH shell via Packages
-
Somebodysh
- Posts: 2
- Joined: Mon Jun 05, 2017 11:35 pm
[Possible bug] Changing SSH shell via Packages
Reposted to the bug trackerShow
Hello! Seems I found a bug in VestaCP 0.9.8/17 (running on CentOS 7.3.1611).
So what did I notice: if you change somebody's SSH shell via Users, changes do appear in /etc/passwd correctly.
But if you change SSH shell in the setting of any Package, it will update all Users using this Package incorrectly - seems like wrong shell parameter is passing when Package changes are triggering Users update.
So, my steps to reproduce this are:
1) Open any package from Packages
2) Change the SSH Access to any new value (I tried to choose "nologin" shell)
3) Save changes and check how Users using this package are updated:
3.1) In the web interface it seems nicely done, showing correct shells
3.2) If you check /etc/passwd file, you will get wrong one there (I've got "sh" shell there)
4) If you do same with single user, you will get right values on both of 3.1 and 3.2 steps
So what did I notice: if you change somebody's SSH shell via Users, changes do appear in /etc/passwd correctly.
But if you change SSH shell in the setting of any Package, it will update all Users using this Package incorrectly - seems like wrong shell parameter is passing when Package changes are triggering Users update.
So, my steps to reproduce this are:
1) Open any package from Packages
2) Change the SSH Access to any new value (I tried to choose "nologin" shell)
3) Save changes and check how Users using this package are updated:
3.1) In the web interface it seems nicely done, showing correct shells
3.2) If you check /etc/passwd file, you will get wrong one there (I've got "sh" shell there)
4) If you do same with single user, you will get right values on both of 3.1 and 3.2 steps