Bug 1388967
Summary: | networking/dovecot - changed default first_valid_uid since rhel-7.3 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Petr Stodulka <pstodulk> |
Component: | preupgrade-assistant-el6toel7 | Assignee: | Jakub Mazanek <jmazanek> |
Status: | CLOSED ERRATA | QA Contact: | Alois Mahdal <amahdal> |
Severity: | medium | Docs Contact: | Lenka Špačková <lkuprova> |
Priority: | unspecified | ||
Version: | 6.9 | CC: | jhornice, jmazanek, msvistun, ovasik, redhat-bugzilla |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | preupgrade-assistant-el6toel7-0.7.1-1.el6 | Doc Type: | Release Note |
Doc Text: |
Users with any UID are now able to log in after the update to RHEL 7
Since Red Hat Enterprise Linux 7.3, the default value of the "first_valid_uid" configuration option of Dovecot changed from "500" in Red Hat Enterprise Linux 6 to "1000" in Red Hat Enterprise Linux 7. Consequently, if a Red Hat Enterprise Linux 6 installation did not have "first_valid_uid" explicitly defined, the Dovecot configuration did not allow users with UID less than "1000" to log in after the update to Red Hat Enterprise Linux 7. Note that only installations where "first_valid_uid" was not explicitly defined were affected. This problem has been addressed by the post-upgrade script, which now changes the "first_valid_uid" value from "1000" to the original value on the source system. As a result, users with any UID are able to log in after the update to Red Hat Enterprise Linux 7.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-11-14 20:40:58 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1429926 |
Description
Petr Stodulka
2016-10-26 15:12:11 UTC
And of course, a info in solution text will be added. For QA: Talk to jmazanek about exact details of the change. Test passed with new build. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:3212 |