Bug 8646

Summary:	cyrus-sasl plugins are provided in subpackages, not installed by default, and lack of them is not hinted by the system
Product:	Mageia	Reporter:	Guillaume cottenceau <gcottenc>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dmorganec, fundawang, guillomovitch, luigiwalser, mageia, stormi-mageia, tmb
Version:	2	Keywords:	Triaged
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	cyrus-sasl-2.1.23-19.mga2.src.rpm	CVE:
Status comment:

Description Guillaume cottenceau 2013-01-10 17:30:26 CET

It took me a couple of hours (!) to understand why Postfix relaying mail with SSL + user authentication failed with "SASL authentication failure: No worthy mechs found" because I lacked "lib64sasl2-plug-plain-2.1.23-19.mga2". Now, usually sub-libraries are split either if they are big (think size of modern hard drives) or if they depend on a lot of unwanted other libraries. None apply to this lib (18k, no deps). Bundling the common "plain, login, you-name-it" mechs in base cyrus-sasl package might avoid majors PITAs... Why is it split?

http://zarb.org/~gc/html/doc-misc.html#2013-01-10

debug postfix logs show this very not useful information:

Jan 10 11:16:24 lmeuh2 postfix/smtp[5997]: starting new SASL client
Jan 10 11:16:24 lmeuh2 postfix/smtp[5997]: name_mask: noanonymous
Jan 10 11:16:24 lmeuh2 postfix/smtp[5997]: smtp_sasl_authenticate: mail.mnc.ch[62.2.77.205]:587: SASL mechanisms PLAIN LOGIN
Jan 10 11:16:24 lmeuh2 postfix/smtp[5997]: warning: SASL authentication failure: No worthy mechs found

(why devs don't show information when dlopen fail might be another worthwhile story)

Thanks

Manuel Hiebel 2013-01-11 23:12:03 CET

CC: (none) => fundawang, guillomovitch

Comment 1 Samuel Verschelde 2013-08-29 15:17:36 CEST

Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

Keywords: (none) => Triaged
CC: (none) => dmorganec, mageia, stormi, tmb

Comment 2 David Walser 2013-08-30 23:57:25 CEST

The description for the cyrus-sasl package does say:
"To actually use SASL you must install at least one of the %{libname}-plug-XXXX
authentication plugin, such as %{libname}-plug-plain."

Maybe there's other places it could be documented that would catch more attention, like a README.urpmi.

I don't think it's wrong at all for it to be split, people can just install whichever plugins they want.  Since it does need at least one to work, maybe all of the plugin packages could Provides: sasl-plug, and then cyrus-sasl could Suggests: sasl-plug, and we could put something in the file urpmi uses to have it prefer libsasl2-plug-plain for that provide.

Anyway, there's no maintainer for this package.  It'd be *really* nice to have one.  Guillaume, any interest in becoming a Mageia packager?

CC: (none) => luigiwalser

Comment 3 Guillaume Rousse 2013-09-01 15:55:56 CEST

Guillaume is correct, there is no added value in shipping every available plugin in distinct subpackages. Just shipping plain, login, and probably anonymous plugins in base package seems a better solution than introducing circular dependencies (plugins requiring base package, and base package requiring at least one plugin).

Comment 4 Guillaume Rousse 2013-09-10 10:34:58 CEST

Actually, I had the same issue with fusioninventory-agent, and I have to concede the soft dependency solution seems a more explicit solution. I'm just waiting for bug #11095 to be fixed first...

Comment 5 Guillaume Rousse 2013-09-29 17:50:30 CEST

I just submitted cyrus-sasl-2.1.26-2.mga4, with a soft dependency on anonymous, plain, and login plugins.

Status: NEW => RESOLVED
Resolution: (none) => FIXED