Bug#618885: Bug#624586: Bug#618885: sasl2-bin: unowned files after purge (policy 6.8, 10.8)

[Patrick Ben Koetter]

* Henrique de Moraes Holschuh <hmh at debian.org>:
> > It has the same semanthics as /etc/shadow.
> 
> Bah, just noticed the semanthics are broken because we have the libs
> outside of / anyway, so if anyone tried to use it for important stuff,
> it is already broken.
> 
> We could purge it, yes, provided it is optional and we ask about it.  It
> needs also to default to NO.  It has to be fool-proof on every possible
> fucked up scenario, and in some of them an admin saying "no!" is the
> only thing that will save him from losing the authentication information
> (passwords) for his users.
> 
> That said, relocating it to outside of /etc is a Major Bad Idea, and I
> very strongly recommend against it.  Local configuration to move it
> somewhere else is already provided, but you just have extreme amount of
> application documentation and even certification tests that want it in
> /etc/sasldb2.

In case we are still interested to find a better location we could team up
with Alexey Melnikov, who is one of the upstream maintainers of Cyrus SASL and
in mail contact with me. He'd be interested to find a better place.

p at rick

-- 
All technical questions asked privately will be automatically answered on the
list and archived for public access unless privacy is explicitely required and
justified.

saslfinger (debugging SMTP AUTH):
<http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>