Back to bug 747334
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Honza Horak | 2011-10-19 14:20:28 UTC | Status | NEW | ASSIGNED |
| Honza Horak | 2011-10-19 14:21:50 UTC | Depends On | 747335 | |
| Tomas Dolezal | 2013-01-03 12:31:17 UTC | CC | todoleza | |
| Ondrej Vasik | 2013-04-18 12:45:24 UTC | Blocks | 947782 | |
| Tom Lavigne | 2014-02-14 14:31:42 UTC | CC | tlavigne | |
| Honza Horak | 2014-02-20 15:10:52 UTC | Priority | unspecified | medium |
| Severity | unspecified | medium | ||
| Petr Sklenar | 2014-04-03 10:00:42 UTC | CC | psklenar | |
| Ondrej Vasik | 2014-11-03 12:52:14 UTC | Blocks | 1159825 | |
| Tomas Kopecek | 2015-08-11 07:42:37 UTC | Assignee | hhorak | mmuzila |
| Tomas Dolezal | 2016-01-18 12:23:20 UTC | QA Contact | qe-baseos-daemons | todoleza |
| Matej Mužila | 2016-01-18 13:27:52 UTC | Status | ASSIGNED | MODIFIED |
| errata-xmlrpc | 2016-01-18 13:47:09 UTC | Status | MODIFIED | ON_QA |
| Honza Horak | 2016-01-20 16:18:01 UTC | Fixed In Version | ypserv-2.19-31.el6 | |
| Matej Mužila | 2016-01-21 10:16:53 UTC | Doc Text | Cause: rpc.yppasswdd doesn't check whether it can write to passwd.adjunct or shadow file. Consequence: rpc.yppasswd returns success even if the operation was not successful. Fix: Added test to check whether the write operation was successful. If the operation was unsuccessful a message is logged. Result: rpc.yppasswdd doesn't return success if the operation was unsuccessful due to unablility to write to /etc/passwd.adjunct or /etc/shadow. |
|
| Tomas Dolezal | 2016-03-09 10:59:01 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2016-05-09 16:28:53 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-05-10 20:33:55 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-05-10 16:33:55 UTC | |||
| Jiri Herrmann | 2016-05-30 15:14:09 UTC | CC | jherrman | |
| Doc Text | Cause: rpc.yppasswdd doesn't check whether it can write to passwd.adjunct or shadow file. Consequence: rpc.yppasswd returns success even if the operation was not successful. Fix: Added test to check whether the write operation was successful. If the operation was unsuccessful a message is logged. Result: rpc.yppasswdd doesn't return success if the operation was unsuccessful due to unablility to write to /etc/passwd.adjunct or /etc/shadow. | Prior to this update, when the yppasswd service failed to change the password of a yppasswdd user, it still reported a success. A test has been added to yppasswdd that verifies whether the write operation was successful. As a result, if yppasswdd fails to change a user password, an error message is now logged about it. | ||
| Lenka Špačková | 2016-05-31 11:08:18 UTC | Docs Contact | jherrman | |
| Doc Text | Prior to this update, when the yppasswd service failed to change the password of a yppasswdd user, it still reported a success. A test has been added to yppasswdd that verifies whether the write operation was successful. As a result, if yppasswdd fails to change a user password, an error message is now logged about it. | *yppasswd* now correctly reports a failure of a user password change Prior to this update, when the *yppasswd* service failed to change the password of a *yppasswdd* user, it still reported a success. A test has been added to *yppasswdd* that verifies whether the write operation was successful. As a result, if *yppasswdd* fails to change a user password, an error message is now logged about it. |
Back to bug 747334