Summary: | qmail requires checkpassword and cmd5checkpw, which aren't always used | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kyle England (RETIRED) <kengland> |
Component: | New packages | Assignee: | Qmail Team (OBSOLETE) <qmail-bugs+disabled> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | minor | CC: | bugzilla-gentoo, mr-russ |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 40486 |
Description
Kyle England (RETIRED)
2005-02-26 15:41:45 UTC
The converse bug to this is the fact that their are multiple checkpassword implementations. Currently only two are in portage. The default, and checkpassword-pam. However qmail requires that checkpassword is installed, as mentioned in the initial report. You should be able to install a different checkpassword. I would like to add, that you can supply a use-flag named "noauthcram" in newest qmail ebuilds. If this flag is supplied, cmd5checkpw really should not be installed! The problem with this is, that if the user decides to enable the corresponding options in conf-smtpd (cmd5checkpw), things will break. Can this be tollerated? I obviously would say yes. ;-) What about a "big fat warning" insde the configfile? Sounds good. I'll implement this. Done in CVS. Can you please check wether it's what you meant? No response in a month, closing. |