On Tue, 16 Dec 2014, Santiago Vila wrote:
Creating the relevant configuration in postinst is what was broken in the
first place. That's why I took it out.
Bug number? References?
Oh there have been various complaints about this or that use case for a
long time. Unfortunately a lot of correspondence took place outside the
BTS but #706216 and #730828 are examples. Here part of the problem was
that originally following upstreams example, the certs were were created
in /etc/ssl but I was asked in #608719 that they be moved to /etc/dovecot
which other people did not want.
#376146 asks to use the snakeoil cert like Ubuntu does but that was not
considered a good idea for Debian when I asked about it.
#763701 was a somewhat embarrassing example of me sucking at shell
scripting. I contacted Mika about his offer to help but he never
wrote back. Alas, this is what always happens when I ask for help.
Looking through the bugs I see that I have been saying since 2005 that
there should be a centralized utility for managing certs that all
packages can use. This is the proper solution and everyone agrees it
should be done but no one does it.
So until that happens it is safest to leave the whole business to the end
user which atleast is no worse than what he would have to do if he
installed dovecot from upstream source.
--
Jaldhar H. Vyas <jald...@debian.org>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
