Bug 883301
Summary: | notifier.conf: MAIL_PASSWORD= <value containing &> is refered to as empty, and fail notifier service start | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Ilanit Stein <istein> |
Component: | ovirt-engine-notification-service | Assignee: | Noam Slomianko <nslomian> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Ilanit Stein <istein> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.1.0 | CC: | bazulay, dfediuck, dyasny, iheim, nslomian, pstehlik, Rhev-m-bugs, sgrinber, ykaul, yzaslavs |
Target Milestone: | --- | ||
Target Release: | 3.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | infra | ||
Fixed In Version: | sf8 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | Bug | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 915537 |
Description
Ilanit Stein
2012-12-04 09:28:58 UTC
Ilanit, does this happen for any password containing this character? in any length? If it only happens if password is a single & character I would close as not fix, this password hardly if ever be found in a real life use case. Not worth the fix. (In reply to comment #1) > If it only happens if password is a single & character I would close as not > fix, this password hardly if ever be found in a real life use case. Not > worth the fix. We were specifically asked in the past to support chars such as !@#$%^&*() We had bugs from customers where they were not supported. This happen for any password containing this character. At any length. (In reply to comment #2) > (In reply to comment #1) > > If it only happens if password is a single & character I would close as not > > fix, this password hardly if ever be found in a real life use case. Not > > worth the fix. > > We were specifically asked in the past to support chars such as !@#$%^&*() > We had bugs from customers where they were not supported. Agree, no problem with that, I was only wandering if it's just an issue with a password with length of one character. At any length as mentioned in comment #3 then it's a bug that needs fixing. Verified on sf-8 3.2 has been released 3.2 has been released |