| Summary: | Sendmail's use of /etc/sasldb2 database is not service-specific | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Philip Prindeville <philipp> |
| Component: | sendmail | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | jskarvad, mlichvar, philipp, redhat-bugzilla |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-12-09 16:00:39 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Attachments: | |||
Created attachment 529710 [details]
Also set default app/realm even if confAUTH_REALM not explicitly set
Created attachment 529711 [details]
Extend list of default SASL mechanisms for sendmail
Created attachment 530203 [details]
Combine the patches to apply directly into fedpkg clone/master.
Also should note that the fix includes turning on digest-md5 for authentication, which doesn't require any optional packages. I disagree at least with the first chunk of attachment #530203 [details], because this
doesn't seem to be generic and does not apply for all authentications.
(In reply to comment #5) > I disagree at least with the first chunk of attachment #530203 [details], because this > doesn't seem to be generic and does not apply for all authentications. Note sure I understand your comment. The standard build of sendmail supports "plain", "login", and "digest-md5" with no additional (optional) packages. See also: https://bugzilla.redhat.com/show_bug.cgi?id=748278 which makes these the standard authentication modes for cyrus-imapd as well. Sendmail might support these mechanisms, but the default configuration of saslauthd is to authenticate against PAM which only supports plain/login, but not digest-md5. Shared secret mechs like this require another plugin at saslauthd. So please do NOT change the default to include "digest-md5". See http://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2006-July/000538.html also. (In reply to comment #7) > Sendmail might support these mechanisms, but the default configuration of > saslauthd is to authenticate against PAM which only supports plain/login, > but not digest-md5. Shared secret mechs like this require another plugin at > saslauthd. So please do NOT change the default to include "digest-md5". See > http://lists.andrew.cmu.edu/pipermail/cyrus-sasl/2006-July/000538.html also. Can you verify this? Because I'm running sendmail.mc as: define(`confAUTH_OPTIONS', `A p')dnl ... TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl define(`confAUTH_REALM', `mail')dnl and Sendmail.conf as: pwcheck_method:saslauthd mech_list:digest-md5 cram-md5 that said, I'm using the /etc/sasldb2 database for authentication. But it works fine. Yes, that issue exists for me together with PAM. Because PAM is the default that is delivered with saslauthd. Can we please continue to ship a non-broken default, that you try to introduce hereby? This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. This bug appears to have been reported against 'rawhide' during the Fedora 23 development cycle. Changing version to '23'. (As we did not run this process for some time, it could affect also pre-Fedora 23 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 23 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora23 This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Created attachment 1223987 [details] Redux not changing mech_list Per comment #9. Created attachment 1224016 [details]
Update to 8.15.2
Attachment #1223987 [details] does at least not break the default SASL authentication
using PAM for me (thus fine), but my scenario should likely not be the only
one to be tested. Maybe Jaroslav has some further ideas or suggestions?
I can't see problem with the latest patch from comment 16, let's try to push it into rawhide. (In reply to Jaroslav Škarvada from comment #18) > I can't see problem with the latest patch from comment 16, let's try to push > it into rawhide. What was the relevant commit? |
Created attachment 529709 [details] Set SASL app/realm for authentication Description of problem: The /etc/sasldb2 may be used to support multiple services, in which case applications leveraging it should specify an app/realm name to avoid ambiguity. Version-Release number of selected component (if applicable): 8.14.5-1 How reproducible: Examine /etc/mail/sendmail.mc Steps to Reproduce: 1. 2. 3. Actual results: AUTH_REALM defaults to the empty string (i.e. resulting in "OAuthRealm" with no value). Expected results: Should use service name (such as "mail", concurrent with cyrus-imapd). Additional info: